LOGIN - UCMD Server configuration option

Owned by Former user (Deleted)
Last updated: Nov 29, 2022 by IT StonebranchVersion comment

Description

The LOGIN option specifies different login information for different operating systems.
 

UNIX and z/OS

The LOGIN option specifies whether or not the shell program that is used to create the user process is invoked as a login shell.
 
A login shell will read and execute commands from the system profile and the user profile. Which profile files are read and executed depends on the type of shell.
 
A non-login shell will not read and execute commands from the profiles. This matches the environment of a process scheduled with cron.

AIX

The AIX platform provides a /etc/environment file within which global environmental variables can be exported for all users of the machine. Universal Command adds the environment variables defined in this file to the user's login environment. The order in which it is processed by Universal Command is slightly different than the AIX login process.
 
The AIX login process reads and processes the following files in the order listed:


 
The LOGIN option directs Universal Command to use the login shell to execute the user command. The AIX login shell does not process the /etc/environment file, so Universal Command processes the files in the following order:

  1. /etc/environment
  2. /etc/profile
  3. $HOME/.profile
  4. $HOME/.env

Windows

The LOGIN option specifies whether or not the user's profile and environment block are loaded by Universal Command and made available to the user process.
 
For purposes of this discussion, a user's profile are those settings listed in the Windows registry under the HKEY_CURRENT_USER key when that user is logged on. This also is known as the user's registry hive.
 
A user's environment block contains the environment variables that are defined for the user when that user is logged on.

IBM i

The LOGIN option specifies whether or not UCMD Server:

Note

LOGIN is used only if the USER_SECURITY option is set to default. If USER_SECURITY is set to none, the initial program inherits the attributes of the invoking job. Thus, setting job attributes would have no consequence. Also, running the initial program from a general profile, if one is specified, may produce unwanted results for some customers. If job customization is desired, the UCMSJOBI exit program should be used.

Usage

Method

Syntax

IBM i

UNIX

Windows

z/OS

Configuration File Keyword

login option

(tick)

(tick)

(tick)

(tick)

Manager Override

n/a





Values

option is the specification for whether or not to:

IBM i

Execute the initial program specified via the CRTUSRPRF and CHGUSRPRF commands and sets the job attributes.

UNIX

Invoke the login shell.

Windows

Load the user's registry hive and environment block.

z/OS

Invoke the login shell.


Valid values for option are:

IBM i


  • yes
    Execute the initial program.
  • no
    Do not execute the initial program.

UNIX


  • yes
    Invoke the shell as a login shell.
  • no
    Do not invoke the shell as a login shell.

Windows


  • yes
    Load the user's registry hive and environment block.
  • no
    Do not load the user's registry hive and environment block.

z/OS


  • yes
    Invoke the shell as a login shell.
  • no
    Do not invoke the shell as a login shell.


Default is no.