BluAGE L3 workshop issue with Go-Live Test batches and Online

Question

After deploying the application and starting successfully, I am not able test successfully both Batch and Online.
1) While submitting TRANBKP job , I see these in the log and jobs ends with a retun code of -1
2024-04-21_08-26-08-259 | [JOB] TRANBKP - Started
2024-04-21_08-26-08-812 | [PROC] REPROC - Started
2024-04-21 06:26:08.844  INFO 2662 --- [      Thread-17] c.n.b.g.i.s.FileConfigurationUtils       : PRC001.FILEIN : BluesamFileConfiguration [bluesamId=, dataset=AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS, cacheCompression=false, warmUp=true, isAnsiCarriageControl=false, disposition=SHR, normal termination=KEEP, abnormal termination=KEEP]

2024-04-21 06:26:08.845  INFO 2662 --- [      Thread-17] c.n.b.g.i.s.FileConfigurationUtils       : PRC001.FILEOUT : GDGSupportConfiguration [relativeGeneration=1, name=AWS.M2.CARDDEMO.TRANSACT.BKUP, ownerPath=., cacheCompression=false, warmUp=true, storageProvider=filesystem, recordSize=350, jobContext=com.netfective.bluage.gapwalk.rt.job.support.DefaultJobContext@1c03ec9e, rdw=false, bdw=false, isFixed=false, isLF=false, isCRLF=false, order=LIFO]

2024-04-21 06:27:46.421  INFO 2662 --- [      Thread-18] c.n.b.gapwalk.utility.idcams.IdcamsPgm   : IDCAMS cmd not computed : /* Copyright Amazon.com, Inc. or its affiliates.                   */

java.lang.NullPointerException: null

2) While executing CC00 online transaction, I get the signin screen however after keying in the User id and password the screen remains on the signin page and don't take me to the menu selection screen. I see this information in the log:
Caused by: java.lang.UnsupportedOperationException: >>> BLUESAM is disabled: Don't use connect when bluesam is disabled

java.lang.UnsupportedOperationException: >>> BLUESAM is disabled: Don't use connect when bluesam is disabled

Note: I am using the correct ARN in bluesam in the carddemo Application definition . My BluAge engine version is 3.2.0.

Accepted Answer

I was able to fix it following these steps.
1) I followed the instructions given https://repost.aws/questions/QU0Xt3tHXERcuo_Az6wWYgrA/bluesam-is-disabled-when-i-try-to-submit-jobs-in-my-carddemo-application
2) In application definition, I gave the parameter as 
bluesam which is incorrect, by reading one of the answers in the post. It must be as below(same as workshop):
"blusam": {
      "db": {
        "secret-manager-arn":

Note: I was able to see and confirm these in the logs post the fix and the BLUESAM  is disabled message was gone.
[ main] c.n.b.g.rt.script.ScriptControlTower : Launching Script Control Tower...
--- [ main] c.n.b.g.b.c.s.WriteBehindPersistence : WriteBehindPersistence using delegate [PgsqlPersistence] with bat
--- [ main] c.n.b.b.a.BluesamAutoConfiguration : Using write behind persistence.
--- [ main] c.n.b.b.a.BluesamAutoConfiguration : Bluesam: GDG metadata support active.
--- [ main] c.n.b.g.b.c.l.redis.RedisBluesamLocker : Bluesam Redis locker successfully activated
--- [ main] c.n.b.g.b.c.l.redis.RedisBluesamLocker : Bluesam Redis locks check level : REBOOT
--- [ main] c.n.b.g.b.c.l.redis.RedisBluesamLocker : Bluesam Redis locks max age : 1000
--- [ main] c.n.b.g.b.c.l.redis.RedisBluesamLocker : Bluesam Redis locker successfully activated
--- [ main] c.n.b.g.b.c.l.redis.RedisBluesamLocker : Bluesam Redis locks check level : REBOOT

.redis.RedisBluesamLocker   : Bluesam Redis locks max age : 1000
sBluesamLocker : Bluesam Redis locks max age : 1000
--- [ main] c.n.b.j.a.TaskRunnerProperties : Expected "runners" to be set; will use default local transaction runner

BluAGE L3 workshop issue with Go-Live Test batches and Online

Conteúdo relevante