Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Unloading issue during automation process in L3 Workshop

2

Hello BluAge Community, hello Experts,

currently I'm digging through the BluAge Level 3 Workshop and am running in some issues, perhaps someone can help me in solving them? The current chapter I'm on is the Execute-section of the Automation-chapter of the workshop.

Here I'm running in a problem during unloading of comparison-data out of the database.

In previous chapters I could solve similar issues by either using 'Server'-option (not Local) while loading data into the database or by removing some encoding-settings in application-utility-pgm.yml

Here in the automation-chapter I'm not able to switch from 'Local' to 'Server'-loading (or unloading?). Has someone perhaps a solution for this topic?

Edit: The issue occurs when launching an ant-run using the file 'execute.xml' in carddemo-automation Project /Edit

The unloading-Problem in console during the test-process:

     [echo] ------------------------------------------------------------------------------------------------------------------------------------------------
     [echo] Unload Bluesam [AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS] to [D:\PhotonUser\Workshop\workspace\carddemo-automation/tests-cases/01-batches/functional-equivalence/bluesam/outputs]
     [echo] ------------------------------------------------------------------------------------------------------------------------------------------------
     [exec] 2024-12-19 06:13:46.944  INFO  --- [             main] Export Bluesam datasets to file system
     [exec] 2024-12-19 06:13:47.337  INFO  --- [             main] Cache 'metadata' created in EhcacheManager.
     [exec] 2024-12-19 06:13:48.640  INFO  --- [             main] Exporting Bluesam dataset: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS
     [exec] 2024-12-19 06:13:48.640  INFO  --- [             main] Opening dataSet AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS ...
     [exec] 2024-12-19 06:13:48.653  INFO  --- [             main] Using regular expression provided through VM argument org.ehcache.sizeof.filters.AnnotationSizeOfFilter.pattern for IgnoreSizeOf annotation : ^.*cache\..*IgnoreSizeOf$
     [exec] 2024-12-19 06:13:48.914  INFO  --- [             main] Detected JVM data model settings of: 64-Bit OpenJDK JVM with Compressed OOPs
     [exec] 2024-12-19 06:13:49.010  INFO  --- [             main] Failed to attach to VM and load the agent: class java.io.IOException: Can not attach to current VM
     [exec] 2024-12-19 06:13:49.040  INFO  --- [             main] Cache 'AWS_M2_CARDDEMO_ACCTDATA_VSAM_KSDS' created in EhcacheManager.
     [exec] 2024-12-19 06:13:49.116  INFO  --- [             main] Loaded 50 records from AWS_M2_CARDDEMO_ACCTDATA_VSAM_KSDS in 74 ms
     [exec] 2024-12-19 06:13:49.195  ERROR --- [             main] Unexpected error while exporint datasets to file system
     [exec] com.netfective.bluage.gapwalk.bluesam.core.metadata.DeserializationException: Expected token: }, read token: persistenceId 
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.metadata.Deserializer$a.parse(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.metadata.Deserializer.a(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.metadata.Deserializer.a(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.metadata.Deserializer.deserializeInternalMetadata(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.storage.rdbms.AbstractRdbmsMetadataPersistence.a(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.storage.rdbms.AbstractRdbmsMetadataPersistence.b(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.storage.rdbms.AbstractRdbmsMetadataPersistence.a(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.storage.rdbms.AbstractRdbmsMetadataPersistence.getInternalMetadata(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.metadata.CoreDataSetMetadata.getInternalMetadata(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.metadata.CoreMetadata.getInternalMetadata(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.CoreDataSet.<init>(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.CoreBluesamManager.a(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.CoreBluesam.a(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.CoreBluesam.a(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.CoreBluesam.open(Unknown Source)
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.Bluesam.open(Unknown Source)
     [exec] 	at aws.bluage.bluesam.export.services.BluesamServices.openBluesam(BluesamServices.java:30)
     [exec] 	at aws.bluage.bluesam.export.services.ExportServices.export(ExportServices.java:38)
     [exec] 	at aws.bluage.bluesam.export.Export.main(Export.java:36)
     [exec] 2024-12-19 06:13:49.199  INFO  --- [             main] Done

Thanks a lot for your assistence Christian

Edit: The command I give: The console above is the output of an ant-run triggering 'Run as' -> 'Ant Build' in eclipse on the file 'execute.xml' in the carddemo-automation project.

  • Didier Durand EXPERT
    2 years ago

    Hi, can you update your question with the command you give (and its parameters) to make answers more relevant? Thks

  • Tama
    2 years ago

    Hi! I see the same error. I've managed to reproduce it running the aws-bluage-bluesam-export.jar in the terminal. Using the commands:

    java -jar aws-bluage-bluesam-export.jar --host=localhost --port=5432 --database=carddemo_bluesam --user=carddemo --password=carddemo --datasets=AWS.M2.CARDDEMO.TRXFL.VSAM.KSDS --outputFolder=D:\PhotonUser\Workshop\workspace\carddemo-automation\utils java -jar aws-bluage-bluesam-export.jar --host=localhost --port=5432 --database=carddemo_bluesam --user=carddemo --password=carddemo --datasets=AWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDS --outputFolder=D:\PhotonUser\Workshop\workspace\carddemo-automation\utils java -jar aws-bluage-bluesam-export.jar --host=localhost --port=5432 --database=carddemo_bluesam --user=carddemo --password=carddemo --datasets=AWS.M2.CARDDEMO.TRANCATG.VSAM.KSDS --outputFolder=D:\PhotonUser\Workshop\workspace\carddemo-automation\utils

    The first one gives the same error and the 2 others run.

  • CeEs
    2 years ago

    Hi Tama, hi all,

    the same situation here. Launching java -jar utils/aws-bluage-bluesam-export.jar --host=localhost --port=5432 --database=carddemo_bluesam --user=carddemo --password=carddemo --datasets=AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS --outputFolder=experimental.outputs in DOS-Prompt gives com.netfective.bluage.gapwalk.bluesam.core.metadata.DeserializationException: Expected token: }, read token: persistenceId at com.netfective.bluage.gapwalk.bluesam.core.metadata.Deserializer$a.parse(Unknown Source) at com.netfective.bluage.gapwalk.bluesam.core.metadata.Deserializer.a(Unknown Source) at com.netfective.bluage.gapwalk.bluesam.core.metadata.Deserializer.a(Unknown Source) at com.netfective.bluage.gapwalk.bluesam.core.metadata.Deserializer.deserializeInternalMetadata(Unknown Source) at com.netfective.bluage.gapwalk.bluesam.core.storage.rdbms.AbstractRdbmsMetadataPersistence.a(Unknown Source) at com.netfective.bluage.gapwalk.bluesam.core.storage.rdbms.AbstractRdbmsMetadataPersistence.b(Unknown Source) at com.netfective.bluage.gapwalk.bluesam.core.storage.rdbms.AbstractRdbmsMetadataPersistence.a(Unknown Source) at com.netfective.bluage.gapwalk.bluesam.core.storage.rdbms.AbstractRdbmsMetadataPersistence.getInternalMetadata(Unknown Source) at com.netfective.bluage.gapwalk.bluesam.core.metadata.CoreDataSetMetadata.getInternalMetadata(Unknown Source) at com.netfective.bluage.gapwalk.bluesam.core.metadata

  • Rupesh
    2 years ago

    Hi all, I am also facing the same issue. Any progress or findings on this one?

  • Kelvin Yeung AWS
    2 years ago

    I also encounter the same Deserialization exception when running the BLuAge Comparein the Automation Batch step: Unexpected error while exporint datasets to file system [exec] com.netfective.bluage.gapwalk.bluesam.core.metadata.DeserializationException: Expected token: }, read token: persistenceId . This error prevent the creation of 4 files. AWS_M2_CARDDEMO_TRANSACT_VSAM_KSDS AWS_M2_CARDDEMO_ACCTDATA_VSAM_KSDS AWS_M2_CARDDEMO_TCATBALF_VSAM_KSDS AWS_M2_CARDDEMO_TRXFL_VSAM_KSDS in the folder of D:\PhotonUser\Workshop\workspace\carddemo-automation\tests-cases\01-batches\functional-equivalence\bluesam\outputs. Other files were created in the same folders without problems: AWS_M2_CARDDEMO_CARDDATA_VSAM_KSDS AWS_M2_CARDDEMO_CARDXREF_VSAM_KSDS AWS_M2_CARDDEMO_CUSTDATA_VSAM_KSDS AWS_M2_CARDDEMO_DISCGRP_VSAM_KSDS AWS_M2_CARDDEMO_TRANCATG_VSAM_KSDS AWS_M2_CARDDEMO_TRANTYPE_VSAM_KSDS AWS_M2_CARDDEMO_USRSEC_VSAM_KSDS. I think we are hitting the same problem. ( I was able to by pass the problem using 'Server'-option (not Local) while loading data into the database or by removing some encoding-settings in application-utility-pgm.yml. I don't know how to fix this error in automation during batch Compare file creation)

Topics
Migration & Modernization
Tags
AWS Blu Age
Language
English

asked 2 years ago510 views

4 Answers
2
Accepted Answer

Hello,

instead of using the project in c:\work\resourses\carddemo-automation, try to donwload the carddemo-automation project as stated here.

AWS

answered 2 years ago

  • Mitra
    2 years ago

    I think they have updated the workshop page. Will check it. Thanks

  • CeEs
    2 years ago

    Hello community, hello cfrezier, hello Alae,

    Thanks a lot for your assistance and coming back to us. TlDr: Exchanging the JAR aws-bluage-bluesam-export.jar in the utils folder of the automation project solves the unloading issue. (Details: aws-bluage-bluesam-export.jar size 17.272.822 bytes, creation date 1/14/2025 10:01 is working) This is the one found in the .zip-archive refered here: https://catalog.us-east-1.prod.workshops.aws/workshops/bf71c0bc-6d8a-4d04-9c10-ab479f7f0e37/en-US/automation/setup

    Some more detail: The aws-bluage-bluesam-export.jar provided in c:\work\resourses\carddemo-automation doesnt necessarily work correctly. In a first evaluation, I just exchanged the .jar in my eclipse-project, nothing else, and it seems to work with the database provided in carddemo-automation\tests-cases\00-default\backups\carddemo_bluesam.backup initially taken from C-drive. Will do further testing now, cheers, Christian

0

Hi,

The jar aws-blueage-bluesam-export.jar from cardemo-automation/utils directory must be updated to match latest version. After that, the export of KSDS files is working.

answered 2 years ago

  • Kelvin Yeung AWS
    2 years ago

    Hi cfrezier, May I ask you for more detail about "updated to match the latest version"? Where can I find the latest version of AWS-Blueage-Bluesam-Export.jar? I can only find a aws-blueage-bluesam-export.jar in the C:\Work\Resources\carddemo-automation\utils folder. That version is the same as the one in the cardemo-automation/utils directory (same size 16,868KB)

  • cfrezier
    2 years ago

    I reached out directly to AWS Team, and they provided me this jar. He told me that he would provide it by either modifying the fleet image or include it in the Workshop. I can't upload it here since there is no option for it.

0

Hello Community, Hello Experts,

it seems that there are some more people experiencing this error. Isnt there anybody out there who can give some valueable hints in solving this?

Thanks a lot, and greets, Christian

answered 2 years ago

-2

The issue you're experiencing during the unloading process in the L3 Workshop automation step is related to a deserialization error. This error occurs when trying to unload the Bluesam KSDS files for comparison, specifically with the AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS file in this case.

The error message suggests there's a problem with the file's metadata structure, as it's expecting a closing bracket (}) but instead encounters a "persistenceId" token. This could be due to a syntax error in the file definition or a potential caching issue.

Unfortunately, switching from 'Local' to 'Server' option isn't possible in the automation chapter as it was in previous steps. However, there are a few things you can try to resolve this issue:

  1. Clear any cached data or temporary files that might be interfering with the unloading process. Sometimes, residual data from previous runs can cause unexpected behavior.

  2. Double-check all configurations and ad-hoc modifications to ensure they've been correctly applied. Incorrect configurations can lead to issues during the automation process.

  3. Verify that you're using the correct version of the workshop tools and executables. The L3 Workshop is designed to work with specific versions, and using an incompatible version could lead to unexpected errors.

  4. If possible, try rerunning the classification step in your code base project. This might help reset file types and resolve any metadata inconsistencies.

  5. Check the CSD (CICS System Definition) file to ensure it contains the expected VSAM file definitions. If the CSD file is incomplete or contains errors, it could lead to issues during the unloading process.

If these steps don't resolve the issue, you may need to reach out to the AWS BluAge support team or the workshop facilitators for more specific guidance. They might be able to provide a targeted solution based on the exact version and configuration of your workshop environment.
Sources
L3 Workshop - Automation - Execute - Unloading of Bluesam KSDS file for compare is failing. | AWS re:Post
L3 Workshop. CSD does not get properly transformed. | AWS re:Post

answered 2 years ago

EXPERT

reviewed 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content