- Newest
- Most votes
- Most comments
I apologize, but I don't have specific information about uploading IBM OS/400 save files to AWS Blu Insights. The sources provided don't contain details about this particular scenario.
However, I can provide some general guidance based on the information available about AWS Blu Insights and its capabilities:
AWS Blu Insights is designed to accelerate mainframe modernization using machine learning and generative AI assistance. It can handle various mainframe languages and file types, but the specific handling of IBM OS/400 save files is not mentioned in the available information.
For your situation, I would recommend the following steps:
-
Ensure that the save file contains the expected COBOL code and associated files.
-
Try to extract the contents of the save file on an IBM OS/400 system if possible, to get access to the individual COBOL source files and data files.
-
If extraction is successful, upload these individual files to AWS Blu Insights rather than the save file itself.
-
If you continue to experience issues, it would be best to contact AWS Support directly. They can provide specific guidance on handling IBM OS/400 save files in Blu Insights or suggest alternative approaches for your mainframe modernization project.
Remember that AWS Blu Insights is designed to simplify tasks such as generating code and file descriptions, transforming code from mainframe languages, and querying projects using natural language. While it may not directly support the .file or .sav extensions you've tried, the underlying capabilities should be able to handle COBOL code once it's in a format the system can recognize.
Sources
AWS Blu Insights accelerates migrations with new AI capabilities - AWS
Relevant content
asked 2 years ago
asked 2 years ago
asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
