ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
File Transfer of SAVF objects between AS400 Agents aborts with ENDED_NOT_OK
Article ID: 84623
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
N/A
File Transfers between 2 AS400 Agents using library objects of the type SAVF abort with a status of ENDED_NOT_OK. An object is created in the target library but it loses its original attributes. It is created as a physical file.
Reference
N/A
File Transfers between 2 AS400 Agents using library objects of the type SAVF abort with a status of ENDED_NOT_OK. An object is created in the target library but it loses its original attributes. It is created as a physical file.
Reference
Automation Engine 11.2 Documentation:
Knowledge Base > Automation Engine and Target System > OS/400 > Agent for OS/400 - FileTransfer Support
Knowledge Base > Automation Engine and Target System > OS/400 > Agent for OS/400 - FileTransfer Support
Cause
Cause type:
By design
Root Cause: To transfer SAVF files within the AE Agent the lib/file must be created first before the file can be sent.
By design
Root Cause: To transfer SAVF files within the AE Agent the lib/file must be created first before the file can be sent.
Environment
OS: IBM AS/400
OS Version: N/A
OS Version: N/A
Resolution
In order to transfer SAVF files within the AE Agents, the process must create the lib/file first before the file can be sent.
For example, before attempting the file transfer the SAVF object can be created on the target system using:
CRTLIB LIB(DESTLIB)
CRTSAVF SAVF(DESTLIB/DEST.SAVF)
This can be completely automated by Automic by creating an action/Workflow to cover this in all aspects and this Workflow can be reused whenever needed.
If this is done before proceeding to the file transfer, the object and its content will be correctly transferred.
Other OS's such as MVS, OS390, and BS2000 behave the same way as the AS400, and for all of them, the solution is to create an action/Workflow. If a new file type is needed create a Workflow for it.
An enhancement to the product to change this behavior would require the submission of a product enhancement.
Fix Status: No Fix
Fix Version(s):
N/A
For example, before attempting the file transfer the SAVF object can be created on the target system using:
CRTLIB LIB(DESTLIB)
CRTSAVF SAVF(DESTLIB/DEST.SAVF)
This can be completely automated by Automic by creating an action/Workflow to cover this in all aspects and this Workflow can be reused whenever needed.
If this is done before proceeding to the file transfer, the object and its content will be correctly transferred.
Other OS's such as MVS, OS390, and BS2000 behave the same way as the AS400, and for all of them, the solution is to create an action/Workflow. If a new file type is needed create a Workflow for it.
An enhancement to the product to change this behavior would require the submission of a product enhancement.
Fix Status: No Fix
Fix Version(s):
N/A
Additional Information
Workaround :
N/A
N/A
Feedback
Yes
No
Powered by
