Batch, Scheduling Agent, and Return Codes


File-AID/EX can be run in Batch mode manually or through the use of a Scheduler on z/ OS or Windows. When a conversion completes, a Return Code is sent to the system. The following sections detail the File-AID/EX Scheduling Agent, Return Codes, and Executing a batch conversion.

File-AID/EX scheduling agent

The File-AID/EX Scheduling Agent is named FEAGENT and is automatically installed on Windows and z/OS during the typical installation procedure for each platform. FEAGENT provides an interface to the File-AID/EX Execution Server from a Scheduler or command line. FEAGENT is designed to start from either a z/OS or WIN32 Scheduler, and upon initialization, sends a message to an active File-AID/EX Execution Server requesting it to start a conversion.

Requirements for calling FEAGENT:

  • The selected Execution Server is running in daemon mode.
  • The xml file is a valid File-AID/EX specification. For assistance in saving specifications as XML files, refer to the online help for each component.
  • The Data Files required to execute the specification reside on the same machine as the Execution Server.

Starting FEAGENT

On z/OS, use JCL to call FEAGENT on a File-AID/EX Execution Server running in daemon mode.

On Windows, start FEAGENT from Win32 using the command line or the WIN32 Scheduler.

To call the Scheduling Agent execute:

FEAGENT <TCP/IP Address><IP Address Port><Execution Type><xml file path><xml file name>
  • <TCP/IP Address> is the TCP/IP address that the File-AID/EX Execution Server is running on
  • <IP Address Port> is the port that the File-AID/EX Execution Server is running on
  • <Execution Type> is ConverterPro / Extract / Loader
  • <xml file path> is the full directory path where the xml file is located. If the directory path contains spaces, add double quotes around it. 

    Important

    The <xml file path> is required when the xml file is not in the default directory:

    <File-AID/EX install path>/Conversion/

  • <xml file name> is the file name with an .xml extension.


Example
feagent 10.17.81.122 4900 ConverterPro c:\samplefiles\usingxml sampleConversion.xml

 Using the default directory: 

Example
feagent 10.17.81.122 4900 Extract sampleExtract.xml

When the specification completes, the File-AID/EX Execution Server sends a Return Code to the FEAGENT, which sends the code back to the calling operation and FEAGENT terminates. Multiple instances of FEAGENT can be created.

Return Code Processing

During batch execution of a File-AID/EX conversion, the File-AID/EX Execution Server writes out a line to the system console describing the results of the Execution. On Windows, this displays in the Execution Server DOS console. When a mainframe batch job completes its execution, check the return code associated with it. The following are the Return codes returned by the File-AID/EX Execution Server:

Code Value

Code String

0

Success: Batch Execution has been successfully completed.

4

Warning: Warnings have occurred with possible database errors.

8

ABEND: The message received is ABEND-specific. Examples of this magnitude include: File not found, Parser Exception, Engine could not be started, etc.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*