Error while accessing User features in test -> online stage(When try to fetch any user account details)

0

Error details:

2024-03-28 04:40:05.877 WARN 3640 --- [nio-8080-exec-7] c.n.b.g.rt.provider.ScriptRegistry : No registered script for the name :[CAVW] 2024-03-28 04:40:05.923 INFO 3640 --- [ taskExecutor-4] c.n.bluage.gapwalk.rt.jics.internal.a : Running Task Registry : added [com.netfective.bluage.gapwalk.rt.jics.internal.TaskContext@7e0cad8d / 4] - [CAVW] 2024-03-28 04:40:05.979 INFO 3640 --- [ taskExecutor-4] org.ehcache.core.EhcacheManager : Cache 'AWS_M2_CARDDEMO_CARDXREF_VSAM_KSDS' created in EhcacheManager. 2024-03-28 04:40:05.987 INFO 3640 --- [ taskExecutor-4] .b.c.s.r.AbstractRdbmsPersistenceSupport : Loaded 50 records from AWS_M2_CARDDEMO_CARDXREF_VSAM_KSDS in 7 ms 2024-03-28 04:40:05.991 INFO 3640 --- [ taskExecutor-4] c.n.b.g.r.j.io.internal.JicsFileBuilder : IMPLICIT OPEN RESULT : JicsResponseCodeHolder [responseCode=NORMAL, resp2=0] 2024-03-28 04:40:05.992 INFO 3640 --- [ taskExecutor-4] o.s.s.support.LifecycleObjectSupport : started org.springframework.statemachine.support.DefaultStateMachineExecutor@4fb8bbf0 2024-03-28 04:40:05.992 INFO 3640 --- [ taskExecutor-4] o.s.s.support.LifecycleObjectSupport : started LOCAL_FINAL _0000_MAIN ABEND_ROUTINE / _0000_MAIN / uuid=d4e5551a-93c7-4738-924a-42b7d5862e7f / id=null 2024-03-28 04:40:05.992 INFO 3640 --- [ taskExecutor-4] o.s.s.support.LifecycleObjectSupport : started org.springframework.statemachine.support.DefaultStateMachineExecutor@2b4b2191 2024-03-28 04:40:05.992 INFO 3640 --- [ taskExecutor-4] o.s.s.support.LifecycleObjectSupport : started FINAL _0000_MAIN_1 LOCAL_FINAL _0000_MAIN ABEND_ROUTINE / _0000_MAIN_1,_0000_MAIN / uuid=8b704bb2-e078-4369-87ba-e9f8bbfe94c9 / id=null 2024-03-28 04:40:05.992 INFO 3640 --- [ taskExecutor-4] o.s.s.support.LifecycleObjectSupport : stopped org.springframework.statemachine.support.DefaultStateMachineExecutor@2b4b2191 2024-03-28 04:40:05.992 INFO 3640 --- [ taskExecutor-4] o.s.s.support.LifecycleObjectSupport : stopped FINAL _0000_MAIN_1 LOCAL_FINAL _0000_MAIN ABEND_ROUTINE / / uuid=8b704bb2-e078-4369-87ba-e9f8bbfe94c9 / id=null 2024-03-28 04:40:05.993 INFO 3640 --- [ taskExecutor-4] c.n.b.g.rt.db.stats.DatabaseStatistics : DATABASE STATISTIC DISABLED 2024-03-28 04:40:06.000 ERROR 3640 --- [ taskExecutor-4] c.n.bluage.gapwalk.rt.jics.internal.a : Unexpected exception: null

java.lang.NullPointerException: null at com.netfective.bluage.gapwalk.rt.jics.io.internal.JicsFileBuilderValidator.checkLength(Unknown Source) at com.netfective.bluage.gapwalk.rt.jics.io.internal.JicsFileBuilder.d(Unknown Source) at com.netfective.bluage.gapwalk.rt.jics.io.internal.JicsFileBuilder.execute(Unknown Source) at aws.bluage.l3.workshop.coactvwc.service.impl.CoactvwcProcessImpl.getcardxrefByacct(CoactvwcProcessImpl.java:396) at aws.bluage.l3.workshop.coactvwc.service.impl.CoactvwcProcessImpl.readAcct(CoactvwcProcessImpl.java:358) at aws.bluage.l3.workshop.coactvwc.statemachine.CoactvwcProcedureDivisionStateMachineService._0000Main(CoactvwcProcedureDivisionStateMachineService.java:185)

Sakthi
posta un mese fa95 visualizzazioni
1 Risposta
3
Risposta accettata

The issue seems to be related to the length or key length of a JICS dataset named CARDXREF.

The key length value is stored in JICS database / table FILE_TABLE / column KEY_LENGTH and set from LISTCAT SQL outputs.

Could you check if this SQL request has been executed?

-- To be used when this VSAM file is referenced in JICS
UPDATE FILE_TABLE SET KEY_LENGTH = 16, RECORD_SIZE = 50 WHERE DS_NAME = 'AWS_M2_CARDDEMO_CARDXREF_VSAM_KSDS';

https://catalog.workshops.aws/aws-blu-age-l3-certification-workshop/en-US/data-migration/datasets/vsam-ksds

Update Jics data
    Open query tool on carddemo_jics database
    Locate Transform SQL output files listcat\sql\cluster\catlg from outputs location
    Execute all queries to update dataset configuration in Jics database
AWS
ArnO
con risposta un mese fa
profile picture
ESPERTO
verificato un mese fa

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande