CHANGE-LOGGING-FILE Change logging file

Privilege                ADA, DA, administrator without domains

This statement closes the previous logging file and opens a new one. The MAREN administrator uses the HOST-NAME operand to specify whether the change of logging file is to apply for his/her own system, for a particular system, or for all systems in a MAREN network.

Format

CHANGE-LOGGING-FILE                                                     Alias: CHLF

FILE-NAME = *STD / <filename 1..54> / <partial-filename 2..30>
,SUPPORT = *PUBLIC-DISK / *PRIVATE-DISK(...)
	*PRIVATE-DISK(...)
		|	VOLUME = <vsn>
		|	,DEVICE-TYPE = <structured-name 1..8>
,HOST-NAME = *OWN / *ALL / <alphanum-name 1..8> /  *ALL-FROM-DOMAIN (...)
	*ALL-FROM-DOMAIN (...)
		|	DOMAIN = *STD-DOMAIN / *OWN / <alphanum-name 1..8>

Operands

FILE-NAME =
Name of the new logging file.

FILE-NAME = *STD
The new logging file is created under the name:

$SYSMAREN.MAREN.LOGGING.yyyymmdd.hhmmss.<systemname>

yyyymmdd hhmmss <system-name>

Current date (ISO4 format) Time of day Name of the local system

FILE-NAME = <filename 1..54>  

If no user ID is specified in the file name, the new logging file is created under the execution ID of MARENCP.

FILE-NAME = <partial-filename 2..30>
The new logging file is created under the name:

<partial-filename 2..30>yyyymmdd.hhmmss.<systemname>

yyyymmdd hhmmss <system-name>

Current date (ISO4 format); Time of day Name of the local system

The last character of <partial-filename 2..30> must be a period.

If no user ID is specified in the file name for <partial-filename 2..30>, the new logging file is created under the execution ID of MARENCP.

SUPPORT =
Location of the new logging file.

SUPPORT = *PUBLIC-DISK
The new logging file is to be created on a public disk.

SUPPORT = *PRIVATE-DISK(...)
The new logging file is to be created on a private disk.

VOLUME = <vsn>
VSN of the disk.

DEVICE-TYPE = <structured name 1..8>
Device type. For a list of possible entries (depending on the BS2000 version), see manual “System Installation” [6].

HOST-NAME =
Specifies the systems for which the logging file is to be changed.

HOST-NAME = *OWN
The logging file is only changed on the local system. If the ADA has used the MODIFY-ADMINISTRATION-SCOPE DOMAIN=... statement to become the DA of a domain, HOST=*OWN addresses the system which was determined by the HOST operand in the MODIFY-ADMINISTRATION-SCOPE statement.

HOST-NAME = *ALL
When domains are used, the logging file is changed for all systems in a DA’s own domain; for the ADA, the logging files are changed for all systems.

HOST-NAME = <alphanum-name 1..8>
Name of a system. If the DA enters the name of a system when domains are being used, this system must belong to the DA’s own domain.

HOST-NAME = *ALL-FROM-DOMAIN (...)
The logging file is changed for all systems of a particular domain. This operand may only be used by the ADA.

DOMAIN =
Selects the domain.

DOMAIN = *STD-DOMAIN
The logging file is changed for the systems in the standard domain.

DOMAIN = *OWN
The logging file is changed for the systems in the local domain. The user’s own domain is the domain of the system on which the ADA is currently working.

DOMAIN = <alphanum-name 1..8>
The logging file is changed for the systems in the specified domain.

Notes

• If the system-specific parameter LOGGING was not set when the MAREN control program was started, no logging file is opened. In this case, execution of the statement is rejected. No logging file is created.

• If other users still have the old log file open, then it will only be closed after these other users access the log file for writing.

• New logging entries are always written to the new logging file.

• If the specified file already exists, it is updated. A further check is carried out to ensure that an existing file possesses the attributes required by a MAREN logging file (ACCESS-METHOD= ISAM, KEY-LENGTH=32, KEY-POSITION=5). Otherwise the statement is aborted. If an error occurs when opening the new logging file even though its file attributes are correct, the MARENCP task is terminated abnormally.

• If a file with the specified name does not exist, a new logging file is opened with the same block size and secondary allocation as the current logging file and in the shared update mode. If the new logging file is to be created on an NK4 pubset, the old logging file must have an even-numbered standard block size, e.g. (STD,2).

Example

//change-logging-file file-name=:data:$sysmaren.marenlog.14.2
%	MARCP32 MAREN LOGGING FILE ':DATA:$SYSMAREN.MARENLOG.14.2' OPENED The current logging file is closed. MAREN creates a new logging file under the user ID SYSMAREN on the pubset DATA and then opens the file in shared update mode.