IBM Support

II02661: DL/1 0806 SCHEDULING ERRORS "PSBATH" IN THE CICS TRACE TABLE SCHEDULE CALL ENTRY.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • REF: A)= DL/I DOS/VS DIAGNOSTIC REFERANCE (SH24-5002
    B)= DL/I APPL PROG: CALL AND RQDLI INTERFACES (SH12-5411)
    
    0806 SCHEDULING ERRORS ARE DESCRIBED IN REF:A PG 2-16/17
    AND REF:B PG 3-3/4 UNDER "CHECKING THE RESPONSE TO A
    DL/I CALL IN A CICS/VS ENVIRONMENT".
    
    0806 SCHEDULING ERRORS CAN BE ISSUED FOR SEVERAL REASONS!  THE
    PSB MAY NOT BE DEFINED IN THE PROGRAM'S ACT ENTRY, THE PSBNAME
    MAY BE TOO LONG (> 7 BYTES) OR MAY NOT BE DELIMITED BY A BLANK
    X'40'.
    
    DETERMINING THE REASON AN 0806 IS ISSUED MAY NOT BE AS
    STRAIGHT FORWARD AS IT SEEMS.  IN ORDER TO DETERMINE WHAT
    CAUSED THE 0806 SCHEDULING ERROR DO THE FOLLOWING.
    
    1.  CHECK YOUR ACTGEN TO INSURE THAT THE PSB NAME DISPLAYED IN
    THE CICS/VS TRACE DL/I SCHEDULING ENTRY (REF:A PG 2-16/17)
    "IS" IN THE ACT.
    
    2.  MAKE SURE THE "PSBNAME" OPERAND OF THE SCHEDULING "CALL"
    IN THE APPLICATION PROGRAM IS A 8 BYTE FIELD. (SEE NOTE)
    
    3.  MAKE SURE THE PSB NAME IS DELIMITED BY BLANKS X'40' AND
    NOT SOME OTHER CHARACTER.
    
    NOTE:  THE CICS/VS TRACE ENTRY FOR A SCHEDULING CALL
    (REF:A PG 2-16/17) DISPLAYS 7 BYTES OF THE 8 BYTE PSB NAME
    (FIELD {UIBPSB} IN THE USER INTERFACE BLOCK {UIB}).  YOU MUST
    INSURE THAT THE BYTE FOLLOWING THE LAST BYTE OF A 7 BYTE PSB
    NAME IN THE TRACE ENTRY IS A BLANK X'40'.  TO DO THIS YOU MUST
    LOOK AT THE PSB NAME IN THE UIBPSB FIELD (UIB +X'28').  IF ANY
    CHARACTER OTHER THAN A BLANK APPEARS IN THE LAST BYTE OF THIS
    FIELD AN 0806 ERROR WILL OCCURE.
    
    ERRORS IN THE NAME OF A PSB THAT IS CORRECT IN THE PSBGEN
    ARE GENERALLY USER ERRORS, POSSIBLY THE NAME OF THE PSB WAS
    PUT INTO A FIELD SHORTER THAN 8 BYTES.
    ADDITIONAL SYMPTOMS:  5746XX100 CALL CALLDLI ASMTDLI CBLTDLI
    PLITDLI
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II02661

  • 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

    1986-10-10

  • Closed date

    1986-10-10

  • Last modified date

    1986-10-16

  • 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