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

L3 Workshop. CSD does not get properly transformed.

0

I am doing L3 workshop and currently at Data Migration. I have followed the instruction as given in the workshop for CICS configuration.

The CSD - CARDDEMO was supposed to transformed and sql file named initjics.sql should have generated with all the VSAM files information in form of queries. But the queries are not getting generated. While the file gets generated with general queries but when in comes to queries related to CSD, none gets generated.

The sql file ends as follows:

-- JICS tables setup -- Generated from CARDDEMO

INSERT INTO JICS_GROUP (NAME) VALUES ;

As you can see that the name of the VSAM file is not even showing up. I have tried various versions of transform engines in Blu Insights and it is all the same. I don't get the complete sql file. Could anyone guide me as where I am going wrong. Is there a configuration that I have missed? Please let me know.

Thank you.

Topics
Migration & Modernization
Tags
AWS Blu Age
Language
English

asked 2 years ago274 views

3 Answers
5
Accepted Answer

Hello, There was some improvements on file types. Go to your code base project and launch the classification again,
this will the set carddemo type to CSDCOMMAD instead of CSD. You can launch the transformation again and see if this solve the issue

Regards

AWS

answered 2 years ago

  • Himaprasad
    2 years ago

    Hi..followed the instructions as mentioned in the answer and the queries got generated as expected. Thank you for helping in resolving this issue.

  • Kelvin Yeung AWS
    2 years ago

    Thank. I resolved the same problem by launching the classification again. This is the right answer.

0

Did you changed the file type to CSD for the CARDDEMO file? Change ist back to CSD COMMAND, trigger the complete project scope again and it should work.

answered 2 years ago

  • Himaprasad
    2 years ago

    Hi..Thank you for the reply. CARDDEMO already had the file type as CSD. I did not make any changes to it. Could you please explain on how to change CSD to CSDCOMMANDS. I could not find a way to do it. I am using version 4.2.0 for L3 workshop.

  • SvenLeiss
    2 years ago

    You can change it in the Codebase -> Assets folder -> Choose CARDDEMO -> Click Launch under the "Manage Extensions" Block -> Change it to CSDCOMMAND. Afterwards generate again. At least this solved the problem for me.

  • Himaprasad
    2 years ago

    Hi..I tried looking in Manage Extensions but all I find is Manage Types and it has a dropdown with types, CSDCOMMAND is not in there. I am unable to manually change the extensions. I am not able to paste the screenshot but the below is textual representation of what is there in Manage types. The target type is a dropdown.

    Manage Types Choose/Edit the type of files without known extension (or .txt) and automatically update files metrics.

    Selected Files Only Current Type Target Type CSD CSD

    Are you using version 4.2.0? Because this version does not have Manage extensions but Manage type and dropdown has CSD but no CSDCOMMANDS.

    Thank you.

0

It seems you're encountering an issue with the CSD (CICS System Definition) transformation during the AWS BluAge L3 Workshop. The problem you're describing, where the initjics.sql file is not properly generated with VSAM file information, could be related to a few potential issues:

  1. CICS configuration: Double-check that you've followed all the CICS configuration steps correctly as outlined in the workshop. Any missed steps in the CICS setup could lead to incomplete transformation.

  2. CSD file content: Ensure that the CARDDEMO CSD file contains the expected VSAM file definitions. If the CSD file is empty or doesn't contain the necessary information, it could result in the incomplete SQL file generation.

  3. Transformation engine version: While you mentioned trying various versions of transform engines in Blu Insights, it's worth confirming that you're using the version recommended for the L3 Workshop. Using an incompatible version could lead to unexpected results.

  4. Ad-hoc modifications: Verify that you've made all necessary ad-hoc modifications related to the workshop, as these can sometimes affect the transformation process.

  5. File permissions and access: Ensure that the transformation process has the necessary permissions to read the CSD file and write the SQL file.

If you've verified all these points and are still experiencing issues, you may need to reach out to the AWS BluAge support team or consult the workshop facilitators for further assistance. They might be able to provide more specific guidance based on the exact version and configuration of the workshop environment you're using.
Sources
AWS Blu Age L3 workshop - Automation step error | AWS re:Post
AWS Blu Age L3 carddemo-web File Error: READ on CXACAIX | AWS re:Post
AWS BluAge L3 Workshop - IMPORT to Eclipse - Archive for required library not resolved | AWS re:Post

answered 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