A fix is available
APAR status
Closed as program error.
Error description
External symptoms: ABENDDM756 issued by SAPIDSP FCT processing for SAPI application Impact to customer: SAPIDSP abend and recovery Analysis: The SAPIDSP's selection criteria matched a job which had been transferred to the system by NJE. The job created a very large number of spinoff datasets. When going through the NJE process bits indicating the output is SPINOFF are not on, so the output is treated as non-spinoff and the spooled OSE's are grouped into a singular OSS control block. The OSSAVAIL halfword value becomes high enough that it is treated as a negative when copied into a fullword field, causing the ABENDDM756. Verification steps: 1) ABENDDM756 issued when processing a job that was transmitted via NJE 2) OSSAVAIL value has high value, such as x'CCF1' Additional symptoms: If another SAPI thread attempts to process the same job's output it can encounter an ABENDDM751 because the OSS abended on has had its eye catcher cleared as part of the clean up from the initial abend. ABENDDM756 can result when any writer attempts to process sysout where the OSSAVAIL value is treated as a negative value. This includes JES3 managed devices and writers using SAPI or PSO to process the sysout. The projected closing code is PER for releases HJS7790 and HJS77A0.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of HJS7790 and HJS77A0. * **************************************************************** * PROBLEM DESCRIPTION: ABENDDM756 when a writer is processing * * sysout for a job. * **************************************************************** * RECOMMENDATION: * **************************************************************** A job had a very large number of sysout data sets and Output Service Elements (IATYOSE) that all had identical sysout characteristics. Output Service Summary elements (IATYOSS) summarize the OSEs that exist for a job and are used when selecting output for a writer. The OSS field OSSAVAIL is a halfword field that is the number of OSEs summarized by an OSS. For the failure, the value was large enough that the high order or sign bit was on. While updating an OSS for sysout to be processed by a writer, code in IATOSGP detected this as an error condition causing the ABENDDM756.
Problem conclusion
Installation On (Global) Order (Any) Activation Order (Any) Type/JES3 restart (Hot) Type/IPL (None) CLPA (No) (See Apar II07968 for definitions) Module IATOSGP was changed so that the value in OSSAVAIL will not exceed X'7000'. When the OSSAVAIL limit is reached, a new OSS will be created to summarize any additional OSEs (IATYOSE) that exist for the job with the same sysout characteristics. IATYOSE was changed to add a new flag byte, OSSFLAG2, and define OSSAVLIM as the limit for OSSAVAIL. The information in the following manuals should appear as indicated below. Updates will only be made to the manuals in future releases. Changes are marked with a "|". GA32-1002-xx JES3 Diagnosis Chapter 4. JES3 Formatted dump Allocated OSS pool ALLOCATED OSS POOL is not formatted in the FSS dump. Only allocated OSS entries are formatted; the entire OSS pool is not formatted. This control block is mapped by the IATYOSS macro. >>> The diagram for ALLOCATED OSS POOL is updated to add >>> a column for FLAG2 and update the contents of the two >>> changed rows. ALLOCATED OSS POOL | LOC RQCHAIN JPTY NEXT PRTY MOSE FLAG1 BUFF | 17C682D8 00000000 02 00000000 02 17C673D0 04 00000005 | RESQUEUE MAXLINES MINLINES TOTLINES AVAIL SCHD | 179C9820 00000006 00000004 0000002A 0008 0000 | OUTBIN FLAG2 | 00000000 00 LOC hhhhhhhh - is the address of the OSS. RQCHAIN hhhhhhhh - is the RESQUEUE chain field. If more than one OSS is required to represent a job's output, this field points to the next OSS. JPTY dd - is the job's priority. NEXT hhhhhhhh - is the pointer to the next OSS chained to the MOSE. PRTY hh - is the output priority. MOSE hhhhhhhh - is the master OSE pointer. | FLAG1 hh - is the OSSFLAG1 field. BUFF hhhh - is the buffer number of the 1st OSE in the OSE chain represented by this OSS. RESQUEUE hhhhhhhh - is the pointer to the RESQ for which the OSS represents output. MAXLINES dddddddd - is the maximum record count. MINLINES dddddddd - is the minimum record count. TOTLINES dddddddd - is the total record count. AVAIL dddd - is the number of OSEs that are available for scheduling. SCHD dddd - is the number of OSEs that are scheduled or in operator hold. OUTBIN hhhhhhhh - is the printer output bin ID in hexadecimal. | FLAG2 hh - is the OSSFLAG2 field. APAR OA47813 prereq's (and sup's) for FMID HJS7790: Pre's: * NONE * APAR OA47813 prereq's (and sup's) for FMID HJS77A0: Pre's: * NONE *
Temporary fix
*** * TEMPORARY FIX MAY BE OBTAINED FROM DLL OR INFO/ACCESS **** ******************* OA47813 DECK AVAILABLE ********************
Comments
APAR Information
APAR number
OA47813
Reported component name
JES3
Reported component ID
5752SC1BA
Reported release
790
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-05-08
Closed date
2015-06-24
Last modified date
2015-08-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA77867 UA77868
Modules/Macros
IATABOS IATIPOSS IATOSGP IATYOSS
GA321002XX |
Fix information
Fixed component name
JES3
Fixed component ID
5752SC1BA
Applicable component levels
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:
03 August 2015