{"id":901,"date":"2017-11-07T21:25:36","date_gmt":"2017-11-07T15:55:36","guid":{"rendered":"http:\/\/zMainframes.com\/zlog\/?p=901"},"modified":"2023-01-20T13:30:14","modified_gmt":"2023-01-20T08:00:14","slug":"jcl-statements-job-statement","status":"publish","type":"post","link":"https:\/\/zmainframes.com\/zlog\/jcl-statements-job-statement\/","title":{"rendered":"JCL statements \u2013 JOB statement"},"content":{"rendered":"

 <\/p>\n

The JOB statement is the very first control statement in a JCL. It marks the start of a job and also specifies the name of the job. The JOB statement is also used to provide certain administrative information, including accounting, security and identification information.<\/p>\n

There will be only 1 JOB statement in a given job.<\/p>\n

JOB Statement Syntax<\/span><\/h2>\n

\"\"<\/p>\n

<\/h3>\n

JOB Name<\/h3>\n

As said earlier, JOB statement marks the beginning of every job and gives a name to the job. Here in above example, the JOB name is \u2018SAMPLE01\u2019.<\/p>\n

The JOB name is \u2013<\/p>\n

    \n
  • Mandatory and will always start at column 3.<\/li>\n
  • The Job name is 1 to 8 bytes in length, which can be alphabetic, alphanumeric or national (#, @, $).<\/li>\n
  • First byte of Job name can be either alphabetic or national. It cannot be numeric.<\/li>\n
  • Job name must be followed by at least 1 blank.<\/li>\n<\/ul>\n

    The JOB name gives an identity of the job to the MVS, in the spool and in the scheduler.<\/p>\n

    Once you submit a job, you can check the execution details of the job in spool using the jobname.<\/p>\n

    (Spool navigation: START -> S -> ST -> PRE <space> jobname<\/em>). (Assumption here is that the site has SDSF to manage the spool. These options might vary for different shops.)<\/p>\n

    You might be wondering, in case, same job with same jobname or some another job with same jobname is submitted multiple times, then how will you identify your submitted job details in spool?<\/em><\/p>\n

    Please remember, when you submit a job, a unique number called as job-number<\/em> is assigned to it by the JES (Job entry subsystem), details of which are generally displayed when job is submitted.<\/p>\n

    Using the Job-name and Job-number combination, you can uniquely identify the log of the job submitted in spool. However, if you\u2019ve SUBmitted a JOB twice with same name, then the \u201csecond Job\u201d will be queued up and wait until the first Job with same name finishes.<\/p>\n

    JOB Keyword<\/span><\/h3>\n

    The literal JOB is used to identify that it is a JOB statement or a JOB card. This is the only keyword to identify a Job-card.<\/p>\n

    Positional Parameters<\/span><\/h3>\n

    In JOB statement, there are 2 Positional parameters:<\/p>\n

    (a)  Accounting Information<\/span><\/h4>\n

    This information is used to identify the person or the department or the organization that will be charged for utilizing the CPU time on mainframe.<\/p>\n

    It should be coded between enclosing parentheses ( ) or apostrophes \u2018\u2019.<\/p>\n

    For example (6621, GROUP2) or \u20186621, GROUP2\u2019. Here we can say, GROUP2 is a group in a given company and the 6621 is the department name in that group.<\/p>\n

    If any special characters are used, enclose the accounting information in apostrophes \u2018\u2019.<\/p>\n

    For example (6621,\u2019GROUP\/2\u2019, 1) or \u20186621, GROUP\/2,1\u2019<\/p>\n

    Length:<\/span> 1 to 143 bytes<\/strong><\/p>\n

    Syntax:<\/span> account-number<\/em><\/strong><\/p>\n

                  \u2018Account-number, other-info\u2019<\/em><\/strong><\/p>\n

                  \u2018Account number\u2019 (for special character<\/strong>s)<\/em><\/p>\n

    Accounting information is mandatory in JOB card and its value may differ across different mainframe shops.<\/p>\n

    <\/h4>\n

    (b)  Programmer Name<\/span><\/h4>\n

    This identifies the person or the group that is responsible for the job. It is not a mandatory parameter.<\/p>\n

    If special characters (other than hyphens, leading or embedded periods) are coded, then the name must be enclosed in apostrophes \u2018\u2019.<\/p>\n

    Programmer name should be coded after accounting information.<\/p>\n

    Length:<\/span> 1 to 20 bytes<\/strong><\/p>\n

    Syntax:<\/span> Name<\/strong><\/p>\n

                   \u2018Name\u2019 (for special characters)<\/strong><\/p>\n

    Key-points for Positional parameters<\/u><\/strong><\/p>\n

    If a positional parameter is omitted, then a comma \u2018,\u2019 has to be coded to indicate the omitted parameter.<\/p>\n

    The replacing comma should not be coded in below scenarios:<\/p>\n

      \n
    • If the positional parameter omitted is the last positional parameter.<\/li>\n
    • If all the positional parameters are omitted.<\/li>\n
    • If all the following positional parameters are omitted.<\/li>\n<\/ul>\n

      <\/h3>\n

      <\/h3>\n

      Keyword Parameters<\/span><\/h3>\n

      The parameters apart from Positional parameters are called Keyword parameters.<\/p>\n

      These keyword parameters can be coded in any sequence following Positional parameters.<\/p>\n

      The Keyword parameters are indicated by coding the keyword sign followed by an equal \u2018=\u2019 sign and the keyword value. (Keyword = Value). E.g. CLASS = A.<\/p>\n

      Unlike Positional parameters, commas \u2018,\u2019 are not used to indicate omission of keyword parameters.<\/p>\n

      There are more than 20 keyword parameters and we will go through the common ones in detail.<\/p>\n

      (a)  CLASS<\/span><\/h4>\n

      In order to improve the efficiency of a batch system, one way is to carefully schedule the work by grouping the jobs with similar resource requirements and this task of grouping similar jobs is done by assigning them to classes.<\/p>\n

      For e.g., a Class A job might need only the standard input and output devices, while the jobs requiring for a printer output might be assigned to Class B.<\/p>\n

      In simple terms, CLASS keyword specifies the job class i.e. the nature of the job.<\/p>\n

      Many mainframe shops do not make use of this option and the CLASS value is set as per the assigned User id.<\/p>\n

      Job CLASSES are set up at JES initialization.<\/p>\n

      Length:<\/span> 01 Byte<\/strong><\/p>\n

      Possible Values:<\/span> A to Z or 0 to 9.<\/strong><\/p>\n

      Syntax:<\/span> CLASS = value<\/strong><\/p>\n

      As mentioned earlier, keyword parameters are optional, so if you do not specify CLASS keyword in the job card, JES will use the installation default specified at initialization.<\/p>\n

      Example<\/strong><\/span><\/p>\n

      \"\"
      (Source: IBM)<\/figcaption><\/figure>\n

      Here, in above example, we can see that the 2 jobs T1 and T2 have been submitted and they are in spool queue. Considering CLASS=A having high priority than CLASS=W, T1 job will be executed first.<\/p>\n

      Please note that the class priority may vary in every mainframe shop. It varies depending on the parameters setup during install.<\/p>\n

      <\/h4>\n

      (b)  MSGCLASS<\/span><\/h4>\n

      While working with JCL, you need to see the execution details or the \u2018job log\u2019 of the JCL submitted. These job logs require memory destination in order to be stored or written.<\/p>\n

      MSGCLASS does this task of determining the output class where the system messages and JCL messages will be written.<\/p>\n

      Length:<\/span> 01 Byte<\/strong><\/p>\n

      Possible Values:<\/span> A to Z or 0 to 9.<\/strong><\/p>\n

      Syntax:<\/span> MSGCLASS = value<\/strong><\/p>\n

      As mentioned earlier, keyword parameters are optional, so if you do not specify MSGCLASS keyword in the job card, JES will use the installation default specified at initialization.<\/p>\n

      Example<\/strong><\/span><\/p>\n

      \"\"
      (Source: IBM)<\/figcaption><\/figure>\n

      <\/h4>\n

      (c)   MSGLEVEL<\/span><\/h4>\n

      MSGLEVEL keyword specifies which JCL statement and JES messages are to be printed in the job log.<\/p>\n

      Syntax:<\/span> MSGLEVEL=(x,y)<\/strong><\/p>\n

      The first sub-parameter of MSGLEVEL controls which statements will be printed in the job log.<\/p>\n

      The second sub-parameter of MSGLEVEL controls which messages will be printed in the job log.<\/p>\n

      Below illustration will clear the MSGLEVEL usage clearly.<\/p>\n

      \"\"As mentioned earlier, keyword parameters are optional, so if you do not specify MSGLEVEL keyword in the job card, JES will use the installation default specified at initialization.<\/p>\n

      Did you notice that parentheses \u2018()\u2019 were included in above syntax. Also, did you wonder why so?<\/p>\n

      Before answering to this, first check how many sub-parameters were coded?<\/p>\n

      2 \u2013 Correct. So, when there are more than 1 sub parameter being coded, you must make use of parentheses \u2018()\u2019.<\/p>\n

      <\/h4>\n

      (d)  Notify<\/span><\/h4>\n

      NOTIFY keyword helps the system determine where to send the job complete information.<\/p>\n

      It causes the system to notify the TSO user mentioned on the NOTIFY parameter when the job completes.<\/p>\n

      Syntax:<\/span> NOTIFY = user-id<\/strong>        – Message will be sent to mentioned user-id. Must be a valid<\/p>\n

      TSO ID.<\/p>\n

                       NOTIFY = &SYSUID<\/strong>  – Messages will be sent to the user-id that was used to submit<\/p>\n

      the job.<\/p>\n

      <\/h4>\n

      (e)  TYPRUN<\/span><\/h4>\n

      TYPRUN keyword modifies the way JES processes the JOB.<\/p>\n

      It checks the JCL and holds the job in the input queue.<\/p>\n

        \n
      • TYPRUN=SCAN<\/strong><\/li>\n<\/ul>\n

        JCL is scanned for errors but is not executed.<\/p>\n

          \n
        • TYPRUN=HOLD<\/strong><\/li>\n<\/ul>\n

          JCL is scanned for errors and if there are any errors, the JCL fails with error notification without execution.<\/p>\n

          If there are no errors, the job is held in queue and it should be released by the user for execution.<\/p>\n

          Release action can be done by typing \u2018A\u2019 against the job name in spool.<\/p>\n

            \n
          • TYPRUN= JCLHOLD<\/strong><\/li>\n<\/ul>\n

            It is similar to HOLD, however, the error check is done only after the job is released by the user.<\/p>\n

            (f)    REGION<\/span><\/h4>\n

            When you submit a JCL, it needs some memory where it can process and execute the required task.<\/p>\n

            The REGION parameter specifies the amount of virtual storage needed by a job\/ job step.<\/p>\n

            It can be coded in JOB statement and EXEC statement as well.<\/p>\n

            Please note,<\/p>\n

              \n
            • If REGION is specified in JOB statement, it applies to each step in the job and overrides the REGION parameter specified in each EXEC statement.<\/li>\n
            • Jobs will abend if some step needs a larger REGION size or if the REGION value cannot be obtained.<\/li>\n
            • REGION must be defined in Steps, when different steps need different amount of space.<\/li>\n<\/ul>\n

              REGION can be specified with the value equal to K (kilobytes) or M (Megabytes)<\/p>\n

              Syntax:  REGION= xx K\/M<\/strong><\/p>\n

              A value equal to 0K or 0M will give job all the storage available.<\/p>\n

               (g)  RESTART<\/span><\/h4>\n

              While working on the data processing, you will definitely face errors. This is a fact and let us accept it.<\/p>\n

              No worries mate! RESTART parameter will help you instruct the system to restart your job after a failure. Of course, the restart action might or might not be successful. It totally depends on what kind of error you have encountered.<\/p>\n

              RESTART parameter forces the JOB execution to start from the mentioned step.<\/p>\n

              Syntax<\/span>: RESTART=step-name<\/strong><\/p>\n

              Example<\/strong><\/span><\/p>\n

              \"\"
              (Source: IBM)<\/figcaption><\/figure>\n

              Please note, in order to make use of the RESTART option, step names must be unique.<\/p>\n

              <\/h4>\n

              (h)  TIME<\/span><\/h4>\n

              \"\"<\/p>\n

              \"\"<\/p>\n

              Most batch systems automatically cancel a program caught in an endless loop after a reasonable time has passed.<\/p>\n

              The data for setting the timer must come from somewhere.<\/p>\n

              This task is done by using the TIME parameter.<\/p>\n

              TIME parameter signifies the maximum time that the JOB or STEP can take to run.<\/p>\n

              It can be coded in both JOB & EXEC statements.<\/p>\n

              If it is coded in both JOB and EXEC statements, the smaller among them will be applicable.<\/p>\n

              Syntax<\/span>: TIME=NOLIMIT     – <\/strong>JOB can utilize the processor for any amount <\/strong>time.<\/strong><\/p>\n

                              TIME = MAXIMUM  – <\/strong>JOB or STEP can be used for maximum amount of<\/strong> time                                                              i.e. 357,912 minutes.<\/strong><\/p>\n

                             TIME = (minutes, seconds)   <\/strong><\/p>\n

              Please note that TIME=1440 is equivalent to coding TIME=NOLIMIT. Thus, 1440 is the only numerical value that is not to be interpreted directly.<\/p>\n

              When there is a time out, the abend code is S322<\/strong>.<\/p>\n

              (i)    PRTY<\/span><\/h4>\n

              It assigns priority to jobs.<\/p>\n

              Consider that there are 2 jobs in a queue with same job class, JES will schedule the job that has high priority first.<\/p>\n

              Priority numbers range from (0-14) or (0-15) depending on the installations.<\/p>\n

              The job with priority coded as 15 has the highest priority and PRTY = 0 has the lowest priority.<\/p>\n

              Syntax<\/span>: PRTY=priority<\/strong><\/p>\n

              Defaults in JCL<\/strong><\/span><\/p>\n

              In above discussion, we have repeatedly mentioned the default values that would be considered in case you don\u2019t mention.<\/p>\n

              Did it strike to you why it is so?<\/p>\n

              Okay, so there are many parameters that can be coded by you programmers in each of the jobs. Instead of coding these parameters, mainframe shops rely on the Defaults.<\/em><\/p>\n

              So, if you fail to mention any keyword and its corresponding value, the system will assume a value by default. However, mostly accounting information and programmer name is required. But, again it will entirely depend on how the JCL in the mainframe shop has been configured. In few shops, it might happen that it will be okay if you don\u2019t provide the accounting information and the programmer name values as well.<\/p>\n

              To override a default, simply code the appropriate parameter.<\/p>\n

              This was all about the JOB statements in a JCL.<\/p>\n

              We will continue with the EXEC statement in the next discussion.<\/p>\n

               <\/p>\n

              \"\"<\/p>\n","protected":false},"excerpt":{"rendered":"

                The JOB statement is the very first control statement in a JCL. It marks the start of a job […]<\/p>\n","protected":false},"author":316,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[28],"tags":[121,125,118,122,129,119,127,128,131,124,120,123,132,117,130,126],"class_list":["post-901","post","type-post","status-publish","format-standard","hentry","category-jcl","tag-dd-statement-in-jcl","tag-difference-between-positional-and-keyword-parameters-in-macro","tag-exec-statement-in-jcl","tag-how-many-job-statements-a-jcl-can-have","tag-jcl-exec-statement","tag-jcl-job-card-programmer-name-length","tag-jcl-parameters-job-card","tag-jcl-parameters-mainframe","tag-list-of-keyword-parameters-in-jcl","tag-list-of-positional-parameters-in-jcl","tag-message-level-in-jcl","tag-msgclassp-in-jcl","tag-msglevel-in-jcl","tag-positional-and-keyword-parameters-in-jcl","tag-positional-parameters-in-dd-statement","tag-positional-parameters-must-be-specified-before-keyword"],"amp_enabled":true,"rttpg_featured_image_url":null,"rttpg_author":{"display_name":"Arpit Patel","author_link":"https:\/\/zmainframes.com\/zlog\/author\/arpitpatel01\/"},"rttpg_comment":7,"rttpg_category":"JCL<\/a>","rttpg_excerpt":"  The JOB statement is the very first control statement in a JCL. It marks the start of a job […]","_links":{"self":[{"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/posts\/901","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/users\/316"}],"replies":[{"embeddable":true,"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/comments?post=901"}],"version-history":[{"count":16,"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/posts\/901\/revisions"}],"predecessor-version":[{"id":1171,"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/posts\/901\/revisions\/1171"}],"wp:attachment":[{"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/media?parent=901"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/categories?post=901"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/tags?post=901"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}