IBM Support

II07301: MSGIKJ56457I LOGON FAILED ALLOCATION UNSUCCESSFUL OR MSGIKJ56457I LOGON FAILED JCL ERROR IN LOGON PROCEDURE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • MSGIKJ56457I LOGON FAILED ALLOCATION UNSUCCESSFUL -or-
    MSGIKJ56457I LOGON FAILED JCL ERROR IN LOGON PROCEDURE
    when logging on to TSO/E. These errors usually occur after
    a LOGON PROC is modified. An example would be specifying
    a comma instead of a period in a dataset name.
    This will cause the LOGON to fail !
    MSGIKJ56400A is issued requesting the user to LOGOFF .
    .
    It is difficult to know what exactly was changed in the LOGON
    PROC because the output from the JCL is usually not kept.
    The following describes how to direct the output to a printer
    on a JES2 system.
    1) Locate the JES2 proc in SYS1.PROCLIB.
    2) Locate the HASPPARM DD in the JES2 proc. This DD will point
       to a dataset/member.
    3) Locate the member in the HASPPARM DD dataset.
    4) Locate TSUCLASS in the member.
    5) MSGCLASS(x) will indicate the OUTCLASS
       OUTCLASS will contain OUTDISP and OUTPUT information.
       Change MSGCLASS to a class that will send data to a printer.
    6) When changing MSGCLASS to a different OUTCLASS, a HOT
       start of JES2 is required.
    7) LOGON, the hardcopy will be sent to the printer. Examine
       output for JCL error or ALLOC error.
    .
    IKJ56457I IKJ56400A 566528502                  IILOGON
    .
    This message can also be issued when a TSO user is
    trying to logon to a system in a sysplex, having previously
    been logged onto another system that has failed.
    Issue $E MEMBER(failing member) on the running system to allow
    the user to logon.
    Or use $T MASDEF,AUTOEMEM=YES,RESTART=YES.
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • Closing Informational APAR.
    

APAR Information

  • APAR number

    II07301

  • 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

    1993-09-28

  • Closed date

    1997-08-14

  • Last modified date

    2000-07-21

  • 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:
14 December 2020