Documentation Changes

The following documentation updates have been made since the last release of this documentation:

Specify Environment Variables—Added note about the environment variable value in the ‘Value’ field.
Resubmit a Failed Job Automatically—Added step about the new ‘Retry step condition’ option applicable only for z/OS-Regular jobs. Added example about restarting a z/OS-Regular job from a specific step when the job fails at another step.
POJO Jobs—Updated notes about setting the CLASSPATH and JAVA_HOME environment variables, changing or redeploying a class or JAR file in the agent installation directory, and restarting an agent.
Define a POJO Job—Added examples about creating a custom Java class and invoking it using POJO Job, instantiating a new class wrapped in a JAR file, and defining a payload consuming job.
Define a DB Trigger Job—Updated notes in the ‘Trigger condition field’. Updated the first example and added examples.
File Transfer Jobs—Updated introduction about the file transfer between a remote location and a remote FTP server.
Define an FTP Job—Updated notes about Run as user in the ‘Local file name’ field. Added default value for the ‘Transfer direction’ and ‘Transfer code type’ fields. Added description for the new ‘Run as User’ field.
Define an SFTP Job—Updated introduction about ASCII support and authentications types. Added default value for the ‘Transfer direction’ field and description for new ‘Transfer code type’ field. Updated ‘User’ field description and notes about authentication. Added note about SFTP server protocol compliance in the ‘The remote os type’ field. Added descriptions for the ‘PrivateKey Path’, ‘PrivateKey passphrase’ fields, and ‘Run as user’ field. Added examples about user authentications, run as user, and SFTP server protocol compliance.
Monitor States—Added description about the ‘Step Complete’ state.
Example: Resubmit a Job if it Completes with a Particular Exit Code Before a Specific Time—Updated this example.
Example: Start an Application if a Job Step in Another Application Completes with a Specific Completion Code—Added this example about the new ‘Step Complete’ monitor state.