AWS mainframe modernization dataset import w/ BluAge & BluSam

Question

i am trying to import a datasets for carddemo deployed on bluage with m2. i would like to import the vsam datasets via the aws cli. I run the following command:

aws m2 create-data-set-import-task --application-id {app_id} --import-config {config_json}

i get a task id. i then run the following to get the status of the task:

aws m2 get-data-set-import-task --task-id {task_id} --application-id {app_id}

and I get the following:

{
    "status": "Failed",
    "summary": {
        "failed": 9,
        "inProgress": 0,
        "pending": 0,
        "succeeded": 1,
        "total": 10
    },
    "taskId": "{task_id}"
}

For the jobs that failed, I'm not seeing logs in cloudwatch or indications of logs in the console. If there a way for me to get a detailed explanation of why the dataset import failed?

re:Post Agent · Answer

I understand you're having trouble importing VSAM datasets for your carddemo application deployed on BluAge with AWS Mainframe Modernization (M2). It's unfortunate that the import task failed for most of the datasets. To get more detailed information about why the dataset import failed, you have a few options:

1. Check the AWS Mainframe Modernization console:
   Navigate to the Applications page, select your application, then go to the Data sets tab. Look for any error messages or status indicators for the failed imports.

2. Use the AWS CLI to get more details:
   You can try using the `describe-data-set-import-task` command instead of `get-data-set-import-task`. This might provide more detailed information about the failure reasons.

```
   aws m2 describe-data-set-import-task --task-id {task_id} --application-id {app_id}
   ```

3. Review your import configuration:
   Ensure that your JSON configuration file for the dataset import is correctly formatted and includes all necessary information for VSAM datasets. Make sure you've specified the correct `datasetOrg`, `encoding`, `format`, `primaryKey`, and `recordLength` values for each VSAM dataset.

4. Check S3 permissions:
   Verify that the M2 service has the necessary permissions to access the S3 bucket where your dataset files are stored.

5. Examine the data files:
   Ensure that the data files in your S3 bucket match the specifications in your import configuration, including file format and encoding.

6. Contact AWS Support:
   If you're still unable to determine the cause of the failures, consider reaching out to AWS Support for assistance. They may be able to provide more detailed logs or insights into the import process.

Remember that when importing VSAM datasets, you need to ensure that the data has been properly transferred from the mainframe to AWS in a format compatible with the BluAge runtime engine. If the data transfer or formatting was incorrect, it could lead to import failures.

If you're able to get more detailed error information, it would help in diagnosing and resolving the specific issues causing the import failures.  
**Sources**  
[AWS Blu Age Blusam - AWS Mainframe Modernization](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-blusam.html)  
[AWS Mainframe Modernization data set definition reference - AWS Mainframe Modernization](https://docs.aws.amazon.com/m2/latest/userguide/datasets-m2-definition.html)  
[Import data sets for AWS Mainframe Modernization applications - AWS Mainframe Modernization](https://docs.aws.amazon.com/m2/latest/userguide/applications-m2-dataset.html)  
[CreateDataSetImportTask - AWS Mainframe Modernization](https://docs.aws.amazon.com/m2/latest/APIReference/API_CreateDataSetImportTask.html)  
[DataSetImportTask - AWS Mainframe Modernization](https://docs.aws.amazon.com/m2/latest/APIReference/API_DataSetImportTask.html)

AWS mainframe modernization dataset import w/ BluAge & BluSam

Relevant content