Description

//         CONCURRENT NAME=name|(name,name,...)...  [comments]

The job specified by a preceding GJOB statement runs concurrently with the jobs specified on NAME= list. The list may contain job names or job set names. The list supports a maximum of 10 elements.

There is no name that is specified on a CONCURRENT statement.

The operation field consists of the characters CONCURRENT and must be preceded and followed by at least one blank. It can begin in any column.

A CONCURRENT statement has one keyword parameter NAME and is required.

Positional Parameters: None.

Keyword Parameters: A CONCURRENT statement can contain the following keyword parameter.

NAME=name

This specifies that the job specified on the preceding GJOB statement must run at the same time (simultaneously) with the jobs specified by the NAME parameter. These jobs must run at the same time on the same JES image. Job names or job set names may be specified.

Note that jobs in a concurrent dependency can have other dependencies that are associated with them. However, all dependencies for all jobs that run concurrently must be met before any of the jobs in the concurrent set start.

The comments field follows the parameter field after at least one intervening blank space. If you do not code any parameters on a JOB statement, do not code any comments.

A CONCURRENT statement is only valid within a job group context and must follow a GJOB statement.

If the system finds an error on the CONCURRENT statement, an HASP1114 message is issued which describes the error. See z/OS JES2 Messages. for more information about the message.

//GRP1        JOBGROUP
//JOB1         GJOB
//JOB2         GJOB 
//              AFTER NAME=JOB1
//              CONCURRENT NAME=(JOB3,JOB4,JOB5)
//JOB6         GJOB
//              CONCURRENT NAME=(JOB3,JOB7)
//JOB3         GJOB
//JOB4         GJOB
//JOB5         GJOB
//JOB7         GJOB
//GRP1        ENDGROUP