SECURITY (Security) Keyword for Intersystem Communications Function Files

Use this file- and record-level keyword to include security information when your program starts a program on a remote system (see the EVOKE keyword). Any record format that has the SECURITY keyword specified for it or implied for it by being specified at the file level must have the EVOKE keyword specified on that record format or implied for that record format by being specified at the file level. If you do not specify the EVOKE keyword, a severe error occurs and the file is not created.

The format of the keyword is:

SECURITY(security-subfield subfield-definition[.3.])

The security-subfield parameter identifies the subfield being defined. This parameter is required. The value specified must be one of the following:

Value
Meaning

1
(Profile ID)

2
(Password)

3
(User ID)

The subfield-definition parameter must be one of the following:

*USER
Indicates that the user profile name of the AS/400 user should be used as the value of the security subfield. For example, if *USER is specified for the password subfield, the user profile name is used as the password.
*NONE
Indicates that a null security value should be used.
'character-string'
You may specify up to 10 characters of security information.
field-name
The specified field contains the security information. The length of the field cannot exceed 10 characters. This parameter is not valid if the SECURITY keyword is specified at the file level.
&field-name
The specified field contains the security information. The length of the field cannot exceed 10 characters. This parameter is not valid if the SECURITY keyword is specified at the file level.

You cannot specify SECURITY with the TIMER keyword.

Option indicators are valid for this keyword.