IBM Support

II04615: HARDWARE: LU1/LU3 PRINTERS WITH ER1 & NOT DR1 IN CICS SENSE0831 POWER-OFF ON LOSE BRACKET STATE SENSE0813 MSGDFH3408/SEE PL36403

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • FOR LUTYPE1 AND LUTYPE 3 PRINTERS, BID REJECTS (0813) CAN OCCUR
    IF AN APPLICATION RUNNING UNDER CICS WAS PRINTING TO A 3270 C/U
    PRINTER THAT WAS POWERED OFF. SENSE0831 IS RETURNED TO THE HOST
    TO INDICATE THIS CONDITION.  AFTER POWERING THE DEVICE BACK ON,
    CICS SHOULD SEND A NEW BID BEFORE SENDING THE NEW DATASTREAM,
    BUT THIS WAS REJECTED WITH SENSE0813, BECAUSE THE CONTROL UNIT
    STILL HAD THE PRINTER IN BRACKET STATE.
    
    THE SESSION WAS BOUND WITH EXCEPTION RESPONSE ONLY (ER1).
    INSTEAD OF DEFINITE RESPONSE (DR1).  WHEN CICS SENT THE FIRST
    DATASTREAM, IT WAS A MULTIPLE RU CHAIN WITH THE END BRACKET
    (EB) ON THE LAST RU.  CICS THEN RESET THE INTERNAL STATE TO
    RECEIVE TO INDICATE BETWEEN BRACKETS (BETB).  THE CONTROL UNIT
    WAITED TILL ALL THE DATA WAS RECEIVED BEFORE SENDING IN THE
    POWER OFF INDICATION, AND FAILED TO RESET THE STATE TO BETB
    FOR THE PRINTER.  THUS THE DATA IS LOST AS WELL AS THE EB
    INDICATION.
    
    LATER, WHEN THE PRINTER IS POWERED BACK UP, CICS SENDS A NEW
    BID, WHICH IS REJECTED WITH SENSE0813 INDICATING A BRACKET STATE
    ERROR SINCE THE DEVICE IS NOT IN THE BETB BRACKET STATE WHEN
    THE BID WITH BEGIN BRACKET (BB) IS SENT FROM CICS.
    
    DATA SENT LAST IN CHAIN (LIC) OR ONLY IN CHAIN (OIC) RQE1 WILL
    OBSERVE BRACKET TERMINATION RULE 1 TO END BRACKET.  THIS RULE
    REQUIRES THE DEVICE TO RESET THE BETB BRACKET STATE, WHICH DID
    NOT OCCUR. PL36403 DOCUMENTS THIS REQUIREMENT.
    
    THIS PROBLEM CAN BE PREVENTED FOR LUTYPE1 OR LUTYPE3 PRINTERS
    USING DR1 DEFINITE RESPONSE MODE FOR APPLICATIONS USING THESE
    PRINTERS.  THIS IS SET BY CODING THE MESSAGE INTERGRITY OPTION
    ON THE PCT DEFINTION (REFERENCE THE RESOUCE DEFINITION MANUAL).
    THE PROBLEM IS LIMITED TO SNA LUTYPE1 AND LUTYPE3 PRINTERS.
    LUTYPE0 FORCES THE USE OF OF DR1.
    
    THE BEST SOLUTION FOR THE PROBLEM, AS DEFINED BY BOTH CICS
    DEVELOPMENT AND HARDWARE DEVELOPMENT IS TO USE DEFINITE
    RESPONSE MODE IN SUCH ENVIRONMENTS WHERE MESSAGE INTEGRITY IS
    NECESSARY.  DEVICES WHICH FAIL TO RESET THE BRACKET STATE TO
    BETB UNDER THESE CONDITIONS SHOULD DOCUMENT THIS FACT IN THE
    APPROPRIATE MANUALS.  IT SHOULD ALSO INDICATE THE DEFINITE
    RESPONSE MODE IS REQUIRED.
    
    FOR SEARCHABILITY:
    MSGDFH3408
    DRQ DR1 ER1 SENSE0831 SENSE0813 3274 PRINTER PRT
    LUSTAT
    MESSAGE INTEGRITY MSGINTEG
    APPLICABLE TO ALL SUPPORTED RELEASES OF CICS
    5740XX100 RG03 RG02
    566540301 R113
    566540301 R310 R311
    

Local fix

  • USE MESSAGE INTEGRITY IN THE PCT OR RDO PROGRAM DEFINITION.
    

Problem summary

Problem conclusion

Temporary fix

Comments

  • CLOSED
    

APAR Information

  • APAR number

    II04615

  • Reported component name

    PB LIB INFO ITE

  • Reported component ID

    INFOPBLIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1990-09-27

  • Closed date

    1990-09-27

  • Last modified date

    1991-08-28

  • 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":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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
13 December 2020