IBM Support

II04452: ABEND0C4 RECEIVED WHEN RUNNING PRINT SERVICES FACILITY IN THE MVS ENVIRONMENT. JES2INFO FSSMODE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • 566527501 HAF1228 R228 AFP/PSF
    569504001 R102 HPRF102
    MSGAPS055I MSGAPS054I MSGAPS051I APSPEFSS
    THIS APAR HAS BEEN CREATED TO HELP DIAGNOSE ABEND0C4 PROBLEMS
    WHEN RUNNING PRINT SERVICES FACILITY IN THE MVS ENVIRONMENT.
    ADDITIONAL INFORMATION WILL BE ADDED AS OTHER PROBLEMS ARE
    IDENTIFIED.  LISTED BELOW ARE COMMON ITEMS TO CHECK WHEN
    RECEIVING THE ABEND0C4. ONE OR MORE OF THESE ITEMS MAY PERTAIN
    TO THE SYSTEM, PLEASE CHECK THEM ALL TO DETERMINE IF THEY APPLY.
    ****************************************************************
    1 - STEPLIB STATEMENTS IN PSF AND/OR JES
    2 - PPT ENTRY MISSING FOR APSPPIEP
    3 - JES2 EXIT 23 ENABLED
    4 - AMODE/RMODE SPECIFICATIONS
    5 - JESFIT SET TO X'40'
    6 - ABEND0C4 USING CHANNEL EXTENDERS
    7 - ABEND02A USING PSF TRACE
    8 - ABEND0C4 PIC 4 at X'126' or X'12A' into APSPPIEP
    ****************************************************************
    ****************************************************************
    1. STEPLIB STATEMENTS.  WHEN UTILIZING STEPLIB STATEMENTS IN
    EITHER THE JES OR THE PSF PROC IT IS CRITICAL TO MAKE SURE THAT
    BOTH PSF AND JES ARE POINTING TO LIBRARIES THAT CONTAIN THE SAME
    LEVEL JES MODULES.  IF THE PSF PROCEDURE AND THE JES
    INITIALIZATION DECK ARE POINTING TO DIFFERENT LIBRARIES, THEN
    THERE IS A HIGH PROBABILITY THAT THE COPY OF THE FUNCTIONAL
    SUBSYSTEM SUPPORT MODULE - CALLED HASPFSSM - THAT IS PICKED UP
    WILL BE DIFFERENT FROM THE OTHER JES MODULES THAT ARE UTILIZED.
    IT IS ALSO POSSIBLE TO PICK UP THE WRONG LEVEL OF ANOTHER
    JES SUPPORT MODULE - HASPSSSM.  TO DETERMINE IF THIS COULD BE
    THE CAUSE OF THE PROBLEM (THE ABEND0C4), GO TO THE SYSTEM DUMP.
    ONCE IN THE DUMP, LOCATE THE RTM2WA SUMMARY SECTION.  ONCE IN
    THAT SECTION, FIND THE PSW AT TIME OF ERROR.  GO TO THE ADDRESS
    IN THE SECOND WORD OF THE PSW AND LOOK AT THE EYECATCHER IN THAT
     AREA.  THE AREA MAY EXPAND BACK SEVERAL PAGES.  LOOK FOR THE
    WORD HASPFSSM OR HASPSSSM IN THE EYECATCHER, IF YOU FIND IT,
    THEN THERE IS A GOOD POSSIBILITY THAT THIS IS THE PROBLEM.
    TO ENSURE THAT THE CORRECT LEVEL OF MODULES ARE BEING PICKED
    UP BY PSF AND JES, VERIFY THAT THE CONCATENATION ON THE
    STEPLIBS FOR THE TWO PROCS ARE THE SAME.
    92/04/01  ADDITIONAL SYMPTOMS: ABEND027 RC0010
    ****************************************************************
    2.  PPT ENTRY MISSING. A CHANGE WAS INTRODUCED WITH MVS/XA 2.2.0
    THAT REQUIRES A PROGRAM PROPERTIES TABLE ENTRY TO BE SET UP FOR
    THE PSF LOAD MODULE APSPPIEP.  THE PPT IS LOCATED IN
    SYS1.PARMLIB IN THE MEMBER SCHEDXX.  THE ENTRY SHOULD LOOK LIKE
    THE FOLLOWING:
    PPTNAME PGMNAME(APSPPIEP)
         KEY(1)
         NOSWAP
         CANCEL
         NOPRIV
         SYST
         NODSI     (THIS IS AN OPTIONAL SETTING)
         PASS
         AFF(NONE)
         NOPREF
    THESE PARAMETERS ARE EXPLAINED IN THE MVS/XA INITIALIZATION AND
    TUNING MANUAL IN THE SYSTEM INITIALIZATION SECTION.  AFTER THIS
    ENTRY IS SET UP, AN IPL OF THE SYSTEM IS REQUIRED TO INCORPORATE
     THE CHANGE.
    ****************************************************************
    3.  JES2 EXIT 23 ENABLED.  THIS JES EXIT CAN LEAD TO AN ABEND0C4
    CONDITION IN PSF WHEN TRYING TO INITIALIZE PSF.  THE EXIT IS A
    USER CODED EXIT.  TO DETERMINE IF THE EXIT IS ENABLED, ENTER THE
    FOLLOWING JES COMMAND FROM THE CONSOLE:
          $D EXIT(23)
    THIS WILL RETURN A HASP823 MESSAGE THAT REPORTS THE STATUS OF
    THE EXIT.  IF THE STATUS IS ENABLED, IT IS POSSIBLE TO DISABLE
    IT WITH THE FOLLOWING JES COMMAND:
          $T EXIT(23),STATUS=DISABLE
    THEN TRY TO REINITIALIZE PSF.  IF IT COMES UP CORRECTLY, THEN
    THERE IS SOME ERROR IN THE EXIT 23 THAT NEEDS TO BE CORRECTED.
    ADDITIONAL SYMPTOMS:  ABEND0C1 HASCSIRQ WITH EXIT 23 ENABLED
    ****************************************************************
      ==>> THIS ITEM PERTAINS TO PSF V1.3.0 HAF1228 ONLY!  <<==
    4.  AMODE/RMODE SPECIFICATIONS.  PSF V1.3.0 IS A PROGRAM THAT
    RUNS BELOW THE 16 MEG LINE IN THE MVS ENVIRONMENT.  IF THE
    AMODE OR RMODE PARAMETER IS SET TO 31-BIT ADDRESSING FOR THE
    SYSTEM, AN ABEND0C4 IN PSF MAY OCCUR.  AN INDICATION OF THIS IS
    THE SECOND WORD OF THE PSW IN THE RTM2WA SUMMARY AREA OF THE
    SYSTEM DUMP FOR THE ABEND0C4.  IF THE HIGH ORDERBIT IS ON IN
    THE SECOND WORD, (IF THE ADDRESS STARTS WITH AN 8.......)
    THEN 31-BIT ADDRESSES ARE BEING ACCESSED.  THIS PARAMETER IS
    SET UP IN THE LINK-EDIT PARAMETERS FOR THE SYSTEM AND CAN BE
    ACCESSED VIA SMP.  BOTH THE AMODE AND THE RMODE NEED TO BE SET
    TO 24 FOR PSF.
    ****************************************************************
    5.  JESFSIT SET TO X'40'.  THIS PROBLEM HAS ARISEN DUE TO AN
    SPE FOR JES2 THAT ALLOWS A NEW TRACE FUNCTION TO BE PERFORMED.
    THERE IS MAINTENANCE REQUIRED BY OTHER COMPONENTS THAT IS
    NECESSARY TO IMPLEMENT THIS TRACE FUNCTION.  THIS MAINTENANCE
    INCLUDES OY22198, OY23160, OY20983 AND OY20769.  SEE APAR
    OY21384 FOR A MORE COMPLETE DESCRIPTION OF THIS SPE.
    DUE TO THE IMPLEMENTATION OF THIS NEW FUNCTION, AN ABEND0C4
    CONDITION HAS OCCURRED IN PSF.  THIS SITUATION MAY VARY IN
    A PARTICULAR SYSTEM BASED ON A FEW FACTORS.  WHEN RUNNING PSF
    IN DEFERRED MODE (THROUGH JES) THE PROBLEM APPEARS TO BE
    INTERMITTENT, BUT OCCURS WHEN THE PRINTER IS STARTED.  IF
    RUNNING PSF IN DIRECT PRINTING MODE THERE IS A 100% FAILURE
    WHEN STARTING THE PRINTER.  TO DETERMINE IF THE JESFSIT
    BYTE IS SET TO X'40' IN THE SYSTEM, FOLLOW THESE STEPS:
    A. LOCATE THE ADDRESS OF THE CVT.  THIS IS FOUND AT X'10' IN
       LOW CORE.
    B. GO TO THAT ADDRESS.
    C. GO +X'128' INTO THE CVT.  THIS IS THE ADDRESS OF THE JESCT.
    D. GO TO THE JESCT.  (THE EYECATCHER WILL SAY JEST.)
    E. GO TO +X'46' INTO THE JESCT.
    F. IF THAT BYTE (JESCT + X'46') IS SET TO X'40' THEN CONTACT
       JES2 FOR CIRCUMVENTION.  THE JES2 APAR THAT ADDRESSES THIS
       ISSUE IS OY28880.  JES COMMON SERVICES MAY ALSO BE CONTACTED
       FOR ASSISTANCE IN THIS AREA.  THEIR COMPID IS 5752SB141.
    ****************************************************************
    6. ABEND0C4 CHANNEL EXTENDERS.  IF USING A CHANNEL EXTENDER TO
       EXTEND PRINTER PROCESSING INSURE THE CHANNEL I/O GEN AND
       PRINTER CONFIGURATION ARE COMPATABLE WITH THE CHANNEL
       EXTENDER CAPABILITIES. (IE: DATA STREAMING OR NON-DATA
       STREAMING FUNCTION)
    ****************************************************************
    7. ABEND02A PSF TRACE. IF PARAMETERS ARE CODED INCORRECTLY TO
       INITIATE PSF NST AND FULL TRACE FACILITIES THIS ABEND CAN
       PUT FROM THE 2 SEPERATE TRACES TO THE SAME SYSOUT FILE.
       SEE JES APAR OY32552
    **************************************************************
    8. AN ABEND0C4 PIC 4 CAN OCCUR AT X'126' OR X'12A' INTO
       APSPPIEP IF YOU HAVE A STEPLIB IN THE PSF STARTUP PROC
       (PRINTDEV) THAT IS NOT APF AUTHORIZED. SEE OPERATING SYSTEM
       INIT & TUNING MANUAL ON HOW TO SET APF AUTHORIZATION.
    **************************************************************
    9. AN ABEND0C4 PIC11 CAN OCCUR IN IAZFSIT AT OFFSET X'9A6'
       (AT HBB5510 LEVEL) IF THERE IS A STEPLIB IN THE JES2 PROC
       AND NOT IN THE PSF PROC.
    

Local fix

Problem summary

Problem conclusion

  • PSPGEC
    

Temporary fix

Comments

  • CLOSING INFORMATION APAR
    

APAR Information

  • APAR number

    II04452

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1990-05-29

  • Closed date

    1990-05-30

  • Last modified date

    2004-03-22

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
13 December 2020