IBM Support

OA44434: MSGHASP107 WHEN PROCESSING JCLLIB STATEMENT AND ORDER= SPECIFIESA DATASET LIST WITH >256 CHARACTERS.**APAR IN ERROR-SEE OA47208

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Under JES2 2.1 (HJE7790):  JOB is submitted with a JCLLIB which
    specifies a list of datasets.  JCLLIB allows a maximum of 15
    datasets.  If the dataset list happens to exceed 256 characters
    (within the limit of 15 datasets), the job will get a JCL
    error ($HASP107).  Ex:
    .
    //PROCS JCLLIB ORDER=(SYS1.PROCLIBTEST1111.TEST1111,
    //            SYS1.TEST2222.SYST2222.PROCLIB.IMSA,
    //            SYS1.TEST3333.SYST3333.PROCLIB.IMSB,
    //            SYS1.TEST4444.SYST4444.PROCLIB.IMSC,
    ...
    //            SYS1.TEST4444.SYST4444.PROCLIB.IMSF)
    .
    When job with above JCLLIB is submitted, only 256 characters
    will be read in starting from "ORDER" leading to a truncated
    JCLLIB statement, causing:
    .
    $HASP107 JEANBR   -- NON-VALID JCLLIB   STMT - VALUE FOR ORDER
    KEYWORD NOT VALID
    .
    Customer impact:
    Jobs meeting above criterias will not run.
    Verification steps:
    - $HASP107
    - A dump will show the truncated JCLLIB card in the JRW data
      area  ($JRW +x'EC' field JRWSTMT).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of HJE7790                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: JES2 incorrectly indicates an error on  *
    *                      a JCLLIB card if the ORDER= value is    *
    *                      greater than 256 characters.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When JES2 is processing the ORDER= keyword on the JCLLIB
    statement, an error is incorrectly indicated if the data sets
    specified result in an operand length that is greater than 256
    characters.  The following message is issued:
    $HASP107 xxxxxxxx -- NON-VALID JCLLIB   STMT - VALUE FOR ORDER
             KEYWORD NOT VALID
    This results in the job failing at conversion time.
    

Problem conclusion

  • TYPE/RESTART(WARM) IPL/REQUIRED(YES) CLPA(YES)
    
             *****************
             * APAR IN ERROR *
             * SEE OA47208   *
             *****************
    
    CLPA is needed only if HASCxxxx modules currently reside in
    the pageable link pack area (PLPA).
    
    Code that parses the JCLLIB statement is updated to not flag
    an error on any keyword other than the PROCLIB keyword.
    
    In addition, an extraneous message was generated when multiple
    PROCLIB= keywords were specified on a single JCLLIB statement.
    The message (shown below) has been eliminated in this case.
      $HASP146 Second JCLLIB statement ignored
    JES2 only honors the first instance of PROCLIB= on the JCLLIB
    statement.  Conversion processing continues to treat multiple
    instances of PROCLIB= as an error which will result in the job
    failing.
    
    Searchable keywords:
    MSGHASP107 MSG$HASP107 MSGHASP146 MSG$HASP146
    
    APAR OA44434 prereq's (and sup's) for FMID HJE7790:
    Pre's: * NONE *
    

Temporary fix

  • *********
                        * HIPER *
                        *********
    *** * TEMPORARY FIX MAY BE OBTAINED FROM DLL OR INFO/ACCESS ****
    ******************* OA44434  DECK AVAILABLE ********************
    

Comments

  • ×**** PE15/06/11 FIX IN ERROR. SEE APAR OA47208  FOR DESCRIPTION
    

APAR Information

  • APAR number

    OA44434

  • Reported component name

    JES2

  • Reported component ID

    5752SC1BH

  • Reported release

    790

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-02-10

  • Closed date

    2014-02-13

  • Last modified date

    2015-06-11

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UA72373

Modules/Macros

  • HASCSRIP
    

Fix information

  • Fixed component name

    JES2

  • Fixed component ID

    5752SC1BH

Applicable component levels

  • R790 PSY UA72373

       UP14/02/26 P F402 Ž

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
11 June 2015