This section describes the effects of ACS on LMS. ACS (Alias Catalog Service) is a BS2000/OSD subsystem which is used to manage alias names for files. An alias name is an arbitrary file name which the user can employ instead of the files’s real name.
Prerequisites
The ACS subsystem must have been started by the system administrator.
An alias catalog in which alias names are unambiguously assigned to real file names must have been generated for the current task.
If a task-specific alias catalog exists, a name specified by the caller of a function accessing a file’s catalog entry will be assumed to be an alias name at first. Only when a name cannot be found in the alias catalog of the task is it then considered to be a real name.
If the specified name is defined as an alias name, it is replaced by the real file name with which it is associated.
Alias names with catalog and user identifiers may cause problems. For more information on working with alias names and on managing the alias catalog, see the section on “ACS” in the manual “Introductory Guide to DMS” [9 (Related publications)].
Handling alias names in LMS
LMS replaces an alias name with the complete member name or file name in accordance with the catalog entry in the following cases:
Adding files
If a file is added as a member using ADD-ELEMENT, LMS always uses the complete file name for the construction of the member name.
Example
Alias name | File name |
X | FILE.X |
The following LMS statement generates the member S/FILE.X/001:
//ADD-ELEMENT FROM-FILE=X,TO-ELEM=*LIB(,ELEM=*BY-SOURCE(VERSION=001),TYPE=S)
Outputting members
If a member is output to a file using EXTRACT-ELEMENT, LMS always uses the complete member name for the construction of the file name.
Example
Alias name | File name |
X | FILE.X |
//EXTRACT-ELEMENT ELEM=*LIB(,ELEM=X,TYPE=S),TO-FILE=*BY-SOURCE
Logging file names
LMS always logs the complete, converted file name.