rh._.exports({"0":[[" ","Using Wait Processing"]],"1":[[" ","Using \n Wait Processing"," ","The BLD, BLDB, and REXEC commands support \n the ability to wait and not return control to Dimensions until the remote \n task being executed has completed."," ","Using \n the BLD, BLDB, and REXEC Commands"," ","Use the following parameters in the \n BLD, BLDB, and REXEC commands to control wait processing:"," ","/BATCH and /NOBATCH"," ","Default: /BATCH "," ","If you specify /NOBATCH, after the BLD \n or BLDB command has run it waits in turn for each of the started jobs. \n You can also set the variable DM_MAX_REXEC_WAIT in dm.cfg to specify the \n longest wait time (in seconds) for the server. If you do not set this \n variable, the server waits indefinitely until the database is updated \n with a job completion record. Each job may succeed or fail. A job may \n also timeout if you have enabled the timeout option."," ","Alternatively, use the RLIST <job-id> \n /WAIT command to achieve the same outcome. If there are different jobs \n being issued, you can achieve a higher degree of parallelism using the \n RLIST facility. You can also use the dm.cfg variable DM_MAX_REXEC_WAIT \n with RLIST."," ","If a BLD or BLDB command starts more \n than one job, use the above mechanism to wait for all of them."," ","Using \n Structured Information Return (SIR)"," ","When a BLD, BLDB or REXEC command is \n started, the variable DM_JOB_ID is returned containing the job ID in the \n form R-uid. If a BLD or BLDB command starts more than one job, DM_JOB_ID \n is the first job started only. In addition, two other variables are also \n returned for the BLD and BLDB commands, DM_JOB_NAME and DM_JOB_STATII. \n Both these variables are arrays."," ","DM_JOB_NAME has elements with \n\t names of the same form as DM_JOB_ID."," ","DM_JOB_STATII has elements containing \n\t SUCCEEDED, FAILED, BACKGROUND, TIMEOUT, or ERROR."," ","BACKGROUND is only seen when \n\t /batch is used."," ","TIMEOUT appears if DM_MAX_REXEC_WAIT \n\t has been exceeded."," ","ERROR only occurs if there \n\t are database errors encountered trying to obtain the job status record."," ","If a build job starts a known number \n of builds, for example three, the syntax looks like this:"," ","BLD \n ... /BATCH"," ","SAVE \n BIG_NAMES DM_JOB_NAME"," ","a:"," ","RLIST \n &(BIG_NAMES(0)). /WAIT"," ","RLIST \n &(BIG_NAMES(1)). /WAIT"," ","RLIST \n &(BIG_NAMES(2)). /WAIT"," ","Build waits for all three jobs to complete, \n and additional processing is done at a: to force a higher degree of parallelism. \n If you use the Dimensions DTK to initiate the processing, the PcmsApi \n functions ","PcmsGetSymbolInfo"," and ","PcmsGetStringSymbolValue"," can obtain and work \n with these data items."," ","Using \n REXEC"," ","Use the following additional parameters \n with /WAIT on the REXEC command:"," ","/CAPTURE"," ","Generates a one time certificate."," ","/BATCH"," ","Distributed platforms: choose \n\t between synchronous and asynchronous execution of the REXEC job."," ","MVS: the started job is always \n\t asynchronous and /NOBATCH does not cause a process to wait."," ","For all platforms, if you use RLIST <job-id> \n /WAIT you have to connect back to Dimensions and issue an RSTAT command \n to update the final status of the job. Failure to do so causes RLIST /WAIT \n processing for this job to wait indefinitely or time out."," ","NOTE  ","Check \n that the client session timeout is less than the maximum time you expect \n to wait for a job or for jobs to complete."]],"id":"430"})