ADLP

not


    Explanation
      When checking the DLI program specification block (PSB), the external security manager checked the usage of the PSB, and found that:

      
        
          The user was unauthorized to access the PSB, or

        

        
          The PSB was unknown to the external security manager, or

        

        
          The user was set to the capability of the default user.

        

      

      The meaning of the term user in the above context depends on the way the transaction was invoked.

      
        
          If the transaction is being run from a local terminal, or has been routed from a remote terminal, the user is the terminal user. (For a routed transaction, if PSBCHK=NO is specified in the SIT, or RESSEC=NO is specified in the transaction definition (CEDA DEFINE TRANSACTION command), the security manager does not check the terminal user.)

        

        
          If the transaction is being run as a result of a request from another CICS MRO region, the user is the owner of the other CICS system (as defined to the external security manager in the JOB statement of the initializing JCL).

        

        
          If the transaction is being run as a result of a request from a connected ISC system, the user is defined in the SECURITYNAME operand of the installed CONNECTION definition that defines the link between the remote system and the local system. Ensure that the name in the SECURITYNAME operand is the same as that supplied by the connected CICS system. This will depend upon the type of CONNECTION between the two systems. For further information about this, refer to the CICS intercommunication.

        

      

      Note: 
        By the above definitions, a PSB used by a routed transaction has two users, the terminal user and the communicating region. Therefore, for routed transactions, the external security manager makes two checks, on the terminal user (as qualified in 1 above), and on the communicating region (2 or 3 above).

      

    

    System action
      The task attempting to schedule the PSB abnormally terminates.

    

    User response
      Ensure that the PSB is defined to the external security manager, and that all users have the correct level of authorization. If the system setup is correct, note the security violation.

    

    Module
DFHDLIRP