GLYPH<SM590000> $DG’MYGROUP’,SUMMARY: Display a summary of a job group.  GLYPH<SM590000> $DG’MYGROUP’,JOBS: Display only job information for the job group.  GLYPH<SM590000> Use the  HOLDUNTL;  keyword to specify that the job must be in the held state until the time  that is specified by the keyword. Then, the job is automatically released and can become  eligible for execution.  GLYPH<SM590000> Use the  STARTBY;  keyword to specify the target execution deadline for the job. GLYPH<SM590000> Use the  WITH;  keyword to indicate that the job must not run unless another (reference) job  is active. When the job runs, the job must run on the same z/OS image as the reference  job.  GLYPH<SM590000> Interval notation: Some number of hours and minutes from the time the job was submitted  to the system. The syntax HOLDUNTL=’+03:20 means that job must be released 3 hours  and 20 minutes after the submission.  GLYPH<SM590000> Point In Time Notation: Direct specification of the time and optionally date when a job must  be released. The syntax HOLDUNTL=(’13:15’,’01/08/2018’) means that job must be  released at 1:15 PM on Aug. 5, 2018. Another job scheduling function is provided by the WITH keyword of the SCHEDULE  statement. The WITH keyword indicates that a job must be selected for execution on the  same system where another job (a reference job) is active. Until a reference job becomes  active, the job that uses WITH function cannot be selected for execution.  STARTBY syntax is identical to the syntax of the HOLDUNTL function. Target time can be  specified in one of the same two formats: Interval or point-in-time notation. By using the STARTBY keyword on the SCHEDULE statement, a user can specify an  approximate time in the future to start the job. The system manages the priority of the job so  that the job is near the top of the relevant job class or service class queue by the target time.  In a sense, this function provides a time-controlled alternative to traditional priority aging.  HOLDUNTL keyword on the SCHEDULE statement tells the system that a job must be  placed in the held state at the submit time and be released at the specified time. HOLDUNTL specifies the time in one of the following formats: You can use these features on their own or together with the JEC to further enhance the job  scheduling capabilities of native work management on z/OS .  The example that is shown in Example 4-1 on page 45 is simple. The 10 new JCL statements  provide the base that can be used to model complex job relationships.  The job log data set for the logging job shows step-by-step information about the execution  flow of the jobs in the job group. Also, the JOBGROUP commands provide the control and  monitoring functions that are needed to maintain a smoothly running job group. JES2 provides functions to hold jobs until a specified time and to make jobs more likely to  start running by a specified time. Various keywords of a SCHEDULE statement provide the  following convenient functions that add flexibility to the job management task:  4.2.2 Deadline scheduling  HOLDUNTL STARTBY WITH 48  A Guide to JES3 to JES2 Migration