Configuring IBM Session Manager on the mainframe

The IBM Session Manager Administration Plug-in and the IBM Session Manager Operations Plug-in are provided in the distribution. To use these Eclipse plug-ins, configure IBM Session Manager on the mainframe with Eclipse support:

  1. Ensure that TCP=Yes is specified on the SYSTEM statement.
  2. Add ECLIPSESERVER port_no as a subparameter of the TCP parameter on the SYSTEM statement, where port_no must not have been specified by any other applications, including other IBM Session Manager systems.
  3. For IBM Session Manager releases prior to 3.2.00, a LOCALNODE parameter must be specified on the SYSTEM statement.
  4. A USER statement must exist for each user of the Eclipse plug-ins; users must sign on through the sign-on dialogue box even if SIGNON NO is specified on the SYSTEM statement.
  5. A special command, ISZECLP, is supplied which has an authority level of 9. When a user attempts to login through an Eclipse plug-in, the user's authority is compared to the authority level of the ISZECLP command and, if equal to or higher, then the user is allowed to login (assuming any subsequent security checks are passed). The authority level on the ISZECLP command may need to be changed depending on your site's requirements. If the user's authority is lower than the level specified for the ISZECLP command then the user will receive message ISZ4297E. In addition, the user must have sufficient authority to issue the QUERY command; if not, message ISZ4297E will appear in the Login dialog.

Common end-user parameters

Two common end-user 'timeout' parameters are associated with use of the Eclipse plug-ins. See ERTIMEOUT and EUTIMEOUT.

Parent topic: