IBM Support

II02668: SYSLOG HELD AFTER WRITELOG. MSGIEF176I WTR DDD WAITING FOR WORK. EXTERNAL WRITER (XWTR).

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • IN RELEASE HJE2330 A USER MODIFICATION IS GENERALLY REQUIRED IN
    ORDER TO HOLD THE DATASETS PRODUCED BY THE SYSLOG STARTED TASK.
    BECAUSE SYSLOG HAS NO JOB CARD, STCMCLASS IS NOT USED.  ALSO
    BECAUSE SYSLOG HAS NO JOB CARD, ITS MESSAGE CLASS IS HARD-CODED
    AS "A".  IN ORDER TO HOLD THE DATASETS PRODUCED BY SYSLOG
    THE SYSOUT CLASS MUST BE "A" AND SYSOUT CLASS "A" (THE MESSAGE
    CLASS) MUST BE DEFINED AS HELD.  JES2 CUSTOMERS DO NOT
    GENERALLY DEFINE CLASS "A" AS A HELD CLASS, HENCE THE USER
    MODIFICATION TO CHANGE THE HARD CODED MESSAGE CLASS TO SOMETHING
    OTHER THAN "A".  WITHOUT THE MODIFICATION, ALTHOUGH USERS MAY
    THINK THE SYSLOG DATASETS ARE HELD BECAUSE THE STCMCLASS AND
    SYSOUT CLASS ARE HELD, THE SYSLOG DATASETS ARE PROBABLY NOT
    HELD.  $L'SYSLOG',ALL AND $L'SYSLOG',H WILL PROVIDE MORE INSIGHT
    INTO WHETHER THE DATASETS ARE HELD OR NOT.  IF AN EXTERNAL
    WRITER IS USED TO PROCESS THE SYSLOG DATASETS THE DATASETS MUST
    BE READY DATASETS (THAT IS, THE DATASETS MUST BE GATHERED INTO
    JOB OUTPUT ELEMENST (JOES)).  IN HJE2330 IT MAY APPEAR THAT THE
    EXTERNAL WRITER IS PROCESSING HELD DATASETS - BUT THAT IS
    NOT THE CASE.  IN HJE2215 THERE IS A NEW INITIALIZATION
    PARAMETER - THE MSGHOLD= PARM ON THE OUTCLASS INIT STATEMENT.
    THIS PARAMETER INDICATES WHETHER OR NOT THE MESSAGE CLASS WILL
    BE CONSIDERED WHEN DETERMINING WHETHER OR NOT A DATASET IS
    HELD.  THIS PARAMETER DEFAULTS TO NO, MEANING THAT IF HOLD=YES
    IS SPECIFIED ON THE OUTCLASS INIT STATEMENT THE SYSOUT WILL BE
    HELD REGARDLESS OF WHAT THE MESSAGE CLASS IS.  IF THE USER HAS
    BASICALLY "CARRIED OVER HIS INIT PARMS" HE WILL PROBABLY HAVE
    THE CLASS THAT THE SYSLOG DATASETS GO TO DEFINED AS A HELD CLASS
    - LIKE HE DID IN HJE2330.  THE ONLY DIFFERENCE HERE IS THAT
    IN HJE2330, ALTHOUGH THE DATASETS WERE DEFINED AS HELD THEY WERE
    NOT, WHEREAS IN HJE1367 OR HJE2215 THE DATASETS ARE DEFINED AS
    HELD AND THEY ARE ACTUALLY HELD.  SINCE THE EXTERNAL WRITER
    CANNOT PROCESS HELD DATASETS IT WILL ISSUE MSGIEF176I INDICATING
     IT IS WAITING FOR WORK. THIS MAY APPEAR TO BE A PROBLEM (BUT IS
    NOT - IT IS A RESULT OF THE DIFFERENCE BETWEEN HELD AND NON-HELD
     DATASETS FROM HJE2330 TO HJE1367/HJE2215).  THE USER
    SHOULD ISSUE THE $O COMMAND TO RELEASE SYSLOG'S HELD DATASETS.
    REFERENCE THE JES2 COMMANDS MANUAL AND THE JES2 INITIALIZATION
    AND TUNING GUIDE TO LEARN MORE ABOUT THE $L AND $O COMMANDS AND
    THE MSGHOLD= PARAMETER OF THE OUTCLASS INITIALIZATION STATEMENT.
    JES2 LEVEL2 CANNOT PROVIDE SUPPORT FOR THE USER MODIFICATION
    REFERENCED EARLIER.  THE MARKETING BRANCH SHOULD BE CONTACTED
    FOR ASSISTANCE IF YOU WISH TO MODIFY JES2 CODE.
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • APAR IS BEING CLOSED FOR INFORMATION ONLY.  JPM.STJ2
    

APAR Information

  • APAR number

    II02668

  • 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

    1986-10-17

  • Closed date

    1986-10-27

  • Last modified date

    1987-02-19

  • 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