IBM Support

II03361: COMMON NETVIEW/ACCESS SERVICES 'NEW USER' PROBLEMS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • 566536501 R102 R103 HZU1102 HZU1103 NVAS
    R104 R105 HZU1104 HZU1105 R200 R201 HZU1200 HZU1201
    THE PURPOSE OF THIS INFORMATION APAR IS TO BE A REPOSITORY OF
    SOME OF THE MORE COMMON NON-DEFECT ORIENTED PROBLEMS WHICH NEW
    USERS OF NETVIEW/ACCESS SERVICES HAVE ENCOUNTERED.
    *
    PROBLEM: MSGEMS0482E 'SUBSYSTEM AUTHORIZATION FACILITY NOT
             AVAILABLE' IS RECEIVED WHEN A USER ATTEMPTS TO LOGON
             TO NV/AS FOR THE FIRST TIME.
    SOLUTION:
    NETVIEW/ACCESS SERVICES IS SHIPPED WITH A DEFAULT USER LOGON
    EXIT, EMSELGNX, WHICH ASSUMES THE USER HAS RACF INSTALLED AND
    ACTIVE (THE EXIT ISSUES RACF MACROS). IF RACF IS NOT INSTALLED
    AND ACTIVE, A USERMOD MUST BE APPLIED TO EMSELGNX TO DISABLE THE
    EXIT, OR THE USER MUST MODIFY EMSELGNX TO HANDLE THE SECURITY
    REQUIREMENTS OF HIS/HER INSTALLATION.
       THERE ARE TWO METHODS WHICH CAN BE USED TO DISABLE THE EXIT,
    EMSELGNX:
       1. AT THE BEGINNING OF THE EXIT, AFTER THE 'USING *,@15'
          STATEMENT, YOU WILL FIND THE ASSEMBLER INSTRUCTION:
                             B     @PROLOG
          REPLACE THIS STATEMENT WITH THE FOLLOWING 2 INSTRUCTIONS:
                             SLR   @15,@15
                             BR    @14
          THIS WILL DISABLE THE USER LOGON EXIT, EMSELGNX, AND
          AND RETURN TO THE CALLER WITH RETURN CODE 0.
          AFTER APPLYING THIS SOURCE MODIFICATION, YOU MUST ASSEMBLE
          EMSELGNX AND LINK-EDIT IT INTO LOAD MODULE EMSELNQH. CSECT
          EMSELNQH MUST ALSO BE INCLUDED DURING THE LINKEDIT, AND
          THE LOAD MODULE, EMSELNQH, MUST BE REPLACED IN THE LOAD
          LIBRARY.
          WHEN YOU LINK-EDIT THE LOAD MODULE EMSELNQH YOU MUST
          HAVE THE CSECT EMSELNQH AS THE FIRST CSECT AS FOLLOWS:
              ORDER EMSELNQH
                SETCODE AC(1)
                MODE AMODE(31),RMODE(24)
                   INCLUDE AEMSMOD0(EMSELNQH)
                   INCLUDE AEMSMOD0(EMSELGNX)
                     ENTRY EMSELNQH
                     NAME EMSELNQH
       2. THE SECOND METHOD OF DISABLING THE USER LOGON EXIT WOULD
          BE TO APPLY THE FOLLOWING USERMOD:
          BE SURE TO CHANGE THE FMID TO THE
          PROPER ONE, FOR THIS ZAP CAN BE USED
          FOR ALL RELEASES.
          ++USERMOD(II03361) .
          ++VER(Z038) FMID(HZU1102) .
          ++VER(Z038) FMID(HZU1103) .
          ++ZAP(EMSELGNX) .
           NAME EMSELGNX
           VER 00 47F0
           REP 00 1FFF,07FE
           IDRDATA II03361
          ***** NOTE *****
       IF THE SPE PTF UL90193 HAS BEEN INSTALLED THE FOLLOWING
       USERMOD MUST BE USED:
          ++USERMOD(II03361) .
          ++VER(Z038) FMID(HZU1102) PRE(UL49447) .
          ++VER(Z038) FMID(HZU1103) PRE(UL49446) .
          ++VER(Z038) FMID(HZU1104).
          ++VER(Z038) FMID(HZU1105).
          ++ZAP(EMSELGNX) .
           NAME EMSELGNX
           VER 00 47F0,F01C
           REP 00 1FFF,07FE
           IDRDATA II03361
    ONCE THE USER LOGON EXIT IS DISABLED, THE USER MAY LOGON TO
    NV/AS USING THE USERID 'PUBUSER' AND ANY NON-BLANK PASSWORD.
    ************************************************************
    FOR NVAS R201, DISABLING OF THE EMSELGNX LOGON EXIT SHOULD
    BE ACCOMPLISHED BY USING THE FOLLOWING ZAP.  APAR PL66324,
    PTF UL77366 SHOULD BE APPLIED AND THEN THE FOLLOWING ZAP
    APPLIED:
    ++USERMOD(II03361).
    ++VER(Z038) FMID(HZU1201) PRE(UL77366).
    ++ZAP(EMSELGNX).
        NAME EMSELGNX
        VER 008C D507,A008
        REP 008C 47F0,B27A
        IDRDATA II03361
      DUE TO CHANGES IN THE LOGON EXIT WHICH CAUSES THIS EXIT TO
    CHECK FOR A USERID OF EITHER 'LOGOFF' OR 'EXIT', THIS IS THE
    METHOD FOR DISABLING THE EMSELGNX FOR HZU1201.  THIS WILL
    ENABLE THE EXIT TO BE DISABLED AND STILL ENABLE THE FUNCTION
    OF USING THE COMMANDS LOGOFF OR EXIT FROM THE USERID FIELD OF
    THE NVAS LOGON PANEL TO BE ACCOMPLISHED.
    *************************************************************
    CAUTION -
    WHEN USING THE "&" VARIABLES SUCH AS UID YOU MAY EXPERIENCE
    A PROBLEM WITH THE USERID BEING REJECTED, BECAUSE IT IS TOO
    LARGE.  YOU WILL SEE THIS IF AN APPLICATION PADS THE USERID
    INPUT FIELD WITH BLANKS, ALLOWS A USERID OF ONLY EIGHT
    CHARACTERS, AND DOESN'T DISCARD ANY BLANKS IN EXCESS OF THE
    EIGHT CHARACTERS.  SOME SUCH APPLICATIONS ARE DESIGNED TO
    ALLOW A USERID OF ONLY EIGHT CHARACTERS (NO MORE, NO LESS).
    IN ORDER TO AVOID RESTRICTING USERS TO AN ID OF ONLY EIGHT
    CHARACTERS, THE APPLICATION WILL PAD THE USERID WITH EIGHT
    BLANKS SO THAT THE USERID CAN BE LESS THAN EIGHT CHARACTERS
    LONG, SINCE IT IS PADDED WITH BLANKS THE APPLICATION
    WILL ACCEPT THE USERID.  HOWEVER, IF THE USERID IS GREATER
    THAN EIGHT CHARACTERS THEN IT IS REJECTED, REGARDLESS OF
    WHETHER THE EXTRA CHARACTERS ARE BLANKS.
    
    ACCORDINGLY, WHEN USING THE &UID FIELD IN NETVIEW ACCESS,
    THE BLANKS MAY CAUSE THE USERID FIELD TO BE GREATER THAN
    EIGHT CHARACTERS.  FOR EXAMPLE, ONCE THE USER KEYS IN &UID,
    THE USERID FIELD WILL CONSISTS OF FOUR CHARACTERS AND
    FOUR BLANKS.  THEN NETVIEW ACCESS WILL SUBSTITUTE THE &UID
    WITH THE REAL USERID, WHICH MIGHT BE SIX CHARACTERS LONG.
    THE INPUT FIELD WILL NOW HAVE SIX CHARACTERS AND FOUR BLANKS.
    THIS IS BECAUSE NETVIEW ACCESS DOES NOT KNOW HOW LONG AN INPUT
    FIELD IS, OR HOW LONG IT SHOULD BE.  THEREFORE, NETVIEW ACCESS
    DOES NOT DISCARD ANY BLANKS.  ACCORDINGLY, THE APPLICATION WILL
    THEN REJECT THE LOGON BECAUSE THE USERID FIELD IS NOW TEN BYTES
    LONG.
    
    IN ORDER TO CIRCUMVENT THIS PROBLEM YOU CAN DO ONE OF THE
    FOLLOWING:
    1.  HIT THE ERASE EOF KEY AFTER KEYING IN THE &UID VARIABLE.
        IF YOU HAVE A USERID OF EIGHT CHARACTERS THEN THIS SHOULD
        WORK.  HOWEVER IF THE USERID IS LESS THAN EIGHT AND THE
        APPLICATION ALLOWS ONLY EIGHT CHARACTERS THEN IT MAY NOT
        WORK.
    2.  IF YOU USE THE &UID THEN HAVE A USERID OF FOUR CHARACTERS.
    3.  DON'T USE THE &UID VARIABLE.
    ****** RE-RECORDING OF AUTOLOGON SEQUENCE *********
    AFTER THE INSTALLATION OF PTFS, IT MAY BE NECESSARY TO
    RE-RECORD THE LOGON SEQUENCE.  PLEASE REFER TO THE FOLLOWING
    LIST:
          PL20831 - NO RE-RECORD NEEDED
          PL21379 - NO RE-RECORD NEEDED
          PL22923 - NO RE-RECORD NEEDED
          PL23001 - NO RE-RECORD NEEDED
          PL27174 - NO RE-RECORD NEEDED
          PL27551 - NO RE-RECORD NEEDED
          PL29704 - NO RE-RECORD NEEDED
          PL29707 - NO RE-RECORD NEEDED
          PL30099 - NO RE-RECORD NEEDED
          PL30238 - NO RE-RECORD NEEDED
          PL26788 - NORMALLY NO RE-RECORD NEEDED.  ONLY RECORDINGS
                    WHICH USE MORE THAN ONE &VAR ON ONE APPLICATION
                    SCREEN COULD NEED A RE-RECORD.
          PL29556 - A RE-RECORD COULD BE NECESSARY FOR CICS ONLY.
    
    ***************************************************************
    IN ORDER TO MAKE NVAS NON-SWAPPABLE THE FOLLOWING STEPS SHOULD
    BE TAKEN:
         1.  FIRST, THE NVAS MAIN LOAD MODULE EMSMAIN MUST BE
             ADDED TO THE PPT TABLE WITH A KEY OF 8 AND A VALUE
             OF NOSWAP.
         2.  SECONDLY, NVAS MUST BE LINKED INTO AN AUTHORIZED
             LIBRARY (APF AUTHORIZED) WITH A NONZERO AUTHCODE
             (IE.  AC(1) ).
    ****************************************************************
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • CLOSING INFO APAR
    

APAR Information

  • APAR number

    II03361

  • Reported component name

    PA LIB INFO ITE

  • Reported component ID

    INFOPALIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1988-04-12

  • Closed date

    1989-06-16

  • Last modified date

    1993-02-01

  • 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":"SG32M","label":"APARs - VSE\/ESA 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"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
13 December 2020