On Wed, 1 Jul 2009 16:17:55 -0500, Mark Zelden <[email protected]> wrote:
>Anyone try to display XEQCOUNT on z/OS 1.9 or z/OS 1.10? I know on z/OS 1.8
>$DJOBCLASS(n) showed it... or at least $DJOBCLASS(n),LONG.
>
>XEQCOUNT doesn't display unless you specifically ask for it, for example:
>
>$DJOBCLASS(A),XEQCOUNT
>
>This is not working as documented for 1.9 or 1.10. According to the FM:
>
>LONG
> Specifies whether an abbreviated list of characteristics is
> provided. An abbreviated display of characteristics is
> provided unless LONG is requested. The abbreviated list
> includes the following characteristics:
>
> MODE
> QAFF
> QHELD
> SCHENV
> XEQCOUNT
> XEQMEMBER
>
>A bug since z/OS 1.9 or WAD or BAD? PMR time... (like I don't have
>better things to do).
>
And the answer is.... A bug!
Guess I should have searched IBMLINK yesterday. APAR OA27859.
It affects z/OS 1.8 through z/OS 1.11. The problem shows up if
the first member defined is not active. Some of our unshared spool
systems have superfluous members defined that are not active.
Coincidentally, the PTFs for the APAR just became available today!
APAR Identifier ...... OA27859 Last Changed ........ 09/07/02
XEQCOUNT MISSING FROM JES2 $D JOBCLASS DISPLAY
Symptom ...... IN INCORROUT Status ........... CLOSED PER
Severity ................... 3 Date Closed ......... 09/06/19
Component .......... 5752SC1BH Duplicate of ........
Reported Release ......... 740 Fixed Release ............ 999
Component Name JES2 Special Notice
Current Target Date ..09/07/10 Flags
SCP ...................
Platform ............
Status Detail: SHIPMENT - Packaged solution is available for
shipment.
PE PTF List:
PTF List:
Release 730 : UA48205 available 09/07/02 (1000 )
Release 740 : UA48206 available 09/07/02 (1000 )
Release 750 : UA48207 available 09/07/02 (1000 )
Release 760 : UA48208 available 09/07/02 (1000 )
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
EXTERNAL SYMPTOMS:
------------------
Entering a $D JOBCLASS or $D JOBCLASS,LONG does not provide
XEQCOUNT display as expected.
Applies to JES2 release 1.8 and above (HJE7730)
IMPACT TO CUSTOMER:
-------------------
See external symptoms.
CAUSE OF ERROR:
---------------
Beginning with JES2 release 1.8, the $D JOBCLASS command keyword
form was changed. The change unintentionally caused XEQCOUNT to
be removed from the display by default.
VERIFICATION STEPS:
------------------
See EXTERNAL SYMPTOMS.
LOCAL FIX:
----------
When entering the jobclass display command, you may force the
display of XEQCOUNT by entering it as part of the display
limiting keywords.
EXAMPLE COMMAND:
$D JOBCLASS(A),XEQCOUNT
RESPONSE:
$HASP837 JOBCLASS(A) XEQCOUNT=(MAXIMUM=10,CURRENT=0)
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: All users of HJE7730, HJE7740, *
* HJE7750, and HJE7760. *
****************************************************************
* PROBLEM DESCRIPTION: XEQCOUNT parameter display is missing *
* from $D JOBCLASS and $D JOBCLASS,LONG *
* commands. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The XEQCOUNT parameter of the $D JOBCLASS command is not
displayed in either the short form or by specifying $D
JOBCLASS,LONG to see all display fields. The value for XEQCOUNT
can be seen by indicating the parameter as a display limiting
option on the command ($D JOBCLASS,XEQCOUNT).
The code processing the $D JOBCLASS command can incorrectly
remove the XEQCOUNT information from the output display if the
first JES2 member it processes for the XEQMEMBER parameter is an
inactive member. The code avoids displaying XEQMEMBER
information for inactive members, and if the first member is
inactive it will also incorrectly avoid displaying the XEQCOUNT
information.
The problem is that the code processing subscripted keywords can
incorrectly remove display data for a prior keyword. If a
prescan exit routine for the current keyword determines that the
first subscripted entry should be skipped, then this can cause
the display data for the prior keyword to be removed.
PROBLEM CONCLUSION:
TYPE/RESTART(WARM) IPL/REQUIRED(YES) CLPA(YES)
CLPA is needed only if HASCxxxx modules currently reside in
the pageable link pack area (PLPA).
The code in HASCSCAN has been changed to correctly
display the information for the prior keyword, even
if the first subscripted item processed for the
current keyword is skipped by a prescan exit
routine.
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[email protected]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
