Syntax rules for follow-up processing on z/OS

The character string enclosed in single quotes may consist of:

• one or more TSO commands separated from one another by semicolons:'command' or 'command;command;command...'

• one or more JCL statements separated from one another by semicolons: 'statement' or 'statement;statement;statement...'
  You can specify the following JCL statements which are identified by their JCL identifier: // "real" JCL statements
  //*        comment lines
  no JCL identifier: in-stream data

• the specific openFT statement 'ALLOC DSNAME(filename)', if a user-created PS data set containing all JCL statements for follow-up processing is to be allocated or

• the specific openFT statement 'ALLOC DSNAME (filename(member-name))' if a usercreated PO or PDSE data set is to be allocated whose member "member-name" contains all JCL statements for follow-up processing.

The specific openFT statement 'ALLOC DSNAME(...' must be entered exactly as specified above. If the TSO command ALLOC is to be specified as follow-up processing, then - unlike the special openFT statement ALLOC DSNAME - the full TSO command name must be specified (i.e. ALLOCATE DSNAME ...).

If one or more TSO commands or one or more JCL statements are specified as follow-up processing, then openFT generates a job that is passed to the system via the internal reader. The FT administrator can adapt uniform job envelopes that are based on the followup processing commands surrounding it to the circumstances of the local system.