User security with LU6.2

User security causes a second check to be made against a user signed onto a terminal, in addition to the link security described in Link security with LU6.2. After reading the following descriptions, consider whether you want the extra level of security checking that user security provides.

You can specify the following levels of user security using the ATTACHSEC parameter of the CONNECTION definition:
  • LOCAL, which you specify if you do not want to make a further check on users by requiring a user identifier or password to be sent. Choose LOCAL if you do not want user security because you consider that the authority of the link is sufficient for your system. See Specifying user security in link definitions for information on doing so.
  • Non-LOCAL, which you specify if you do want to make a further check on users by requiring a user identifier, or a user identifier and a password, to be sent. Non-LOCAL includes the following types of checking:
    • IDENTIFY

      A user identifier must be sent, but no password is requested

    • VERIFY

      A password must also always be sent

    • PERSISTENT VERIFICATION

      Password is sent on the first attach request for a user

    • MIXIDPE

      Either identify or persistent verification

Note: Non-LOCAL user security verification further describes these types of user checking. See Specifying user security in link definitions for information on specifying them.