The CFS userlib is a user-specific library, in which CFS procedures, Command memory elements (created with a Save Memory command), and dialog segments (LOG files) are stored.

The userlib has a standard name of CFS.USERLIB. Each userid can thus access their own userlib.

The command UL lib is available to the user to assign a different library. This change can also be made in the CFS SET mask.

Only PLAM libraries should be used as userlibs, as from BS2000 Version 8. All elements should be of type S (Source).

A DO xxxxx | RET xxxxx command will be handled by CFS as follows:

If lib(element) or %name is specified, then the procedure to be processed will have been uniquely identified. In all other cases, the following hierarchy will apply:

a) CFS will look in the assigned userlib (Standard: CFS.USERLIB) for an element with the specified name.

b) An element with the specified name will be sought in the secondary userlib. The secondary userlib can be assigned with a /FILE ...,LINK=USERLIB command, or the standard library name of $user-id.CFS.USERLIB.STD will be used. $user-id is the userid under which the CFS program phase is stored.

c) A file with the specified name will be sought.

Global procedures can be stored in a secondary userlib. This userlib can only be created as a single library, under the name $user-id.CFS.USERLIB.STD. $user-id is the userid under which all files relating to CFS are stored (e.g. CFS, CFSLIB, CFSHELP).

The user can also assign another secondary userlib with a FILE command as follows: /FILE userlib,LINK=USERLIB.

Elements from the userlib can also be used with LM (Load Memory) and RES (Restore Dialog) commands. In contrast to the DO and RET commands, the LM xxxxx and RES xxxxx commands always refer to a file with this name. If a library element is being referred to, it must be fully specified as follows: userlib(xxxx).