USE Records

USE records indicate the MCP options that are to be used.

Most of these MCP options need not be set in the MCP configuration file. You can use the SO and RO system commands to set and reset, respectively, most of these options when the MCP is operational.

The TO === system command lists the status of all these options. The TO = system command lists only those options that can be set or reset when the MCP is running.

A cold-start resets all USE system options to those specified in the MCP configuration file. A halt/load returns the system to any settings that might have been changed since a cold-start.

_ USE <option> _______________________________________________________________________| 
                |                           |
                |_ <additional parameters> _|

USE AFTR Record

The AFTR record automatically removes programs from the schedule that are associated with another job that either has been removed from the schedule or has been terminated abnormally. Such jobs must be associated with the AFTER command.

USE APBD Record

The APBD record indicates that when a printer backup file with an AUTO record in its file-equate statement is closed, the file is to be printed automatically.

USE APCR Record

The APCR record directs the MCP to automatically place pseudo card decks into pseudo card readers as the decks are closed or as they appear on disk or disk pack. If this record is not set, you must use the RN system command to accomplish this action (refer to the description of the RN and RNP commands in Volume 2).

USE AUHL Record

The AUHL record automatically initiates a halt/load in the event of a system failure, unless that failure originates during a halt/load.

USE AURD Record

The AURD record automatically removes pseudo-reader decks from disk if those files contain erroneous control instructions. If the AURD record is reset, any decks containing erroneous control instructions must be removed manually.

USE BOJ Record

The BOJ record displays beginning-of-job (BOJ) messages each time a job enters the active mix.

USE CHRG Record

The CHRG record specifies that all programs must have a charge number in order to execute. For security purposes, this record can be set only at a cold-start.

If you use a ZIP command to initiate a program but the command syntax does not supply a charge number for that program, the system uses the assigned charge number of the program.

_ USE CHRG ___________________________________________________________________________| 
            |                   |                                                       
            |_ <charge number> _|                                                       
            |                   |                                                       
            |_ ALL _____________|                                                       

The charge number is a 6-digit number that must be used when initiating system utilities. If you do not designate a charge number, 999999 is used by default.

The keyword ALL declares that charge numbers are required for all MCP utilities in which charge numbers can be specified.

USE CLOS Record

The CLOS record displays a file-closed message each time a program closes a file.

USE COPY Record

The COPY record displays a message each time the SYSTEM/COPY utility transfers or compares a file. If the COPY record is not set, the messages are not displayed.

USE DATE Record

The DATE record requires that a date be entered during a halt/load.

USE DBUG Record

The DBUG record indicates that you use the MCP and user debug facility, and causes the DBUG module to be loaded into memory.

When a fault in the MCP occurs, the following statements apply:

  • If the USE DBUG record is used, a memory dump is taken if no memory dump has occurred in the last five minutes. If a dump has occurred, a prompt is given that allows to take another memory dump or to preserve the original. If the CONTROL DEBUG MCP record is used, the system halts temporarily. If you press the SPCFY key, the system resumes operating and terminates the task.
  • If the USE DBUG record is not used, no memory dump or temporary halt occurs.

USE DCOM Record

The DCOM record causes a data communication module to be loaded into memory when a data communication device is activated.

USE DCP Record

The DCP record causes a DCP to be loaded into memory. This module must be present for a DCP to be used on the system.

Because an MCP network information file (MCPNIF) must be on the system disk of the processor when the USE DCP record is used, this record should not be present in the MCP configuration file. Using this record automatically initiates a load host (LH) command to all DCPs declared in the MCPNIF.

USE DMS2 Record

The DMS2 record causes the DMS2 extension module to be loaded into memory. The DMS2 module is required in order to use the data management facilities available in the COBOL-74, RPG, and Pascal programming languages.

USE DUMP Record

The DUMP record directs the MCP dump file to a specific disk or disk pack medium. The MCP file name is $p0001, where p represents the processor number.

The dump file can be directed to tape, disk, or disk pack. You must use the DMPMEM utility to dump the MCP dump file to tape. The I/O path information to those disk or disk pack dump files is stored in memory during system operation. Because of this, the physical path to the medium (that is, the channel and unit designation) cannot be changed without performing a halt/load.

_ USE DUMP ___ DISK __________________________________________________________________| 
            |        |                      | |                                         
            |        |_ SUBSYSTEM <number> _| |                                         
            |                                 |                                         
            |_ PACK __________________________|                                         
            |        |                 |      |                                         
            |        |_ <family name> _|      |                                         
            |                                 |                                         
            |_ TAPE __________________________|                                         

If you specify DISK, the system dumps the file to disk. The optional subsystem number specifies the logical disk subsystem to which to dump the file. The logical subsystem number is in the range 1 to 8.

If you specify PACK, the system dumps the file to an unrestricted disk pack. The optional family name specifies a particular disk pack family to which to dump the file. Specifying TAPE indicates that the dump is not to reside on disk or disk pack. You must use the DMPMEM utility to manually dump the file if specify TAPE. The TAPE record invalidates the 0 DM command (refer to the description of the DM command in Volume 2).

Examples

USE DUMP DISK
USE DUMP DISK SUBSYSTEM 14
USE DUMP PACK
USE DUMP PACK NAMEOF
USE DUMP PACK BACKUP
USE DUMP TAPE

USE EOJ Record

The EOJ record displays an end-of-job (EOJ) message each time a program comes to an end of a job.

USE GTDK Record

The GTDK record forces program trace requests to a backup disk. If this record is not used, the trace request goes to an available line printer. The trace request does not specify a backup disk or originate from a timesharing job.

USE LIB Record

The LIB record causes a message to be displayed each time a file is removed or changed.

USE Logging Records

These records indicate whether you want the system to maintain the Run Log (RLOG), the SPO Log (SLOG), the Network Log (NLOG) and the Maintenance Log (MLOG). You must declare one record for each log you want to use. The NOSTGO and NOCALL options apply to the Run Log (RLOG) only

Note: By default, the MLOG is maintained. Use the USE MLOG record to change the options for MLOG.

                  |<_____________________________|
                  |                              |
_ USE ___ MLOG _______________________________________________________________________| 
       |        |   |                          |
       |_ SLOG _|   |_____________ <log size> _|
       |        |   |  |        |              |
       |_ NLOG _|   |  |_ SIZE _|              |
                    |                          |
                    |_ AUTO ___________________|
                    |                          |
                    |_ WRAP ___________________|
                    |                          |
                    |_ NOBUFFER _______________|
              |<_____________________________|
              |                              |
_ USE _ RLOG _________________________________________________________________________| 
                |                          |
                |_____________ <log size> _|
                |  |        |              |
                |  |_ SIZE _|              |
                |                          |
                |_ AUTO ___________________|
                |                          |
                |_ WRAP ___________________|
                |                          |
                |_ NOBUFFER _______________|
                |                          |
                |_ NOSTGO _________________|
                |                          |
                |_ NOCALL _________________|
SIZE <log size> Sets the size of the log file. The size must be in the range from 100 to 10000 sectors, rounded to the closest 100. If you do not specify a log file size, the system uses 1000 sectors by default.

The log is transferred and renamed automatically when the file is full. Otherwise, the log transfers when it is the specified time of day for the log transfer to take place or when the LN or TL system commands force the transfer. Log transfer time is set with the LOGXFRTIME control record.
AUTO Automatically processes the log after it is transferred (refer to the description of the LOGXFRTIME control record for more information).
WRAP Renames the log files before each transfer by incrementing a number in the file name from 0 to 9. For example, the name of the Maintenance Log (MLOG) can change from MLOG#1 to MLOG#9, where # is the processor number. If you do not use this option, the file names do not change and a log file overwrites the previous file at log transfer time. If you do not use the option, the MLOG files are named MLOG#0 and MLOG#1.
NOBUFFER Prevents the operating system from buffering log records. The operating system attempts to buffer these records in order to reduce the frequency of I/O requests against the log file. You should specify this option only when there is no active system dump file.
NOSTGO Indicates that job-stopped and job-resumed records are not to be logged. The option is valid only for the Run Log (RLOG).
NOCALL Indicates that program-call and program-return records are not to be logged. The option is valid only for the Run Log (RLOG).

Examples

USE MLOG AUTO 2000
USE RLOG AUTO SIZE 1600 WRAP
USE SLOG 2000 NOBUFFER WRAP

USE MICR Record

The MICR record causes a reader-sorter module to be loaded into memory. This module must be in memory for reader-sorters to function.

USE OPEN Record

The OPEN record displays a file-open message each time a program opens a file.

USE PBD Record

The PBD record routes printer backup files to disk. If you use more than one of the printer backup routing records, the system uses the following priority order to route the files: printer, tape, disk pack, and disk.

USE PBP Record

The PBP record routes printer backup files to disk pack. If you use more than one of the printer backup routing records, the system uses the following priority order to route the files: printer, tape, disk pack, and disk.

USE PBPS Record

The PBPS record directs all areas of printer and punch backup files to a single disk pack, if disk pack is the selected medium. This record is used in conjunction with the USE PBP record.

USE PBT Record

The PBT record routes printer backup files to a scratch tape on a readied drive. As long as the drive remains ready, the tape can be used by one program after another, until it fills up with files.

If the drive is not ready, the tape remains a printer backup tape. The printing mechanisms stop and wait to resume printing when the drive becomes ready again.

Printer backup files can be routed to other places besides tape. If you use more than one of the printer backup routing records, the system uses the following priority order to route the files: printer, tape, disk pack, and disk.

USE PCD Record

The PCD record indicates that punch card backup files are to be built on disk. Punch card backup files can be routed to other places besides disk. If you use more than one of the backup routing records, the system uses the following priority order to route the files: card punch, printer, disk pack, and disk.

USE PCH Record

The PCH record directs punch files to the card punch. If you use more than one of the punch backup routing records, the system uses the following priority order to route the files: disk pack and disk.

USE PCP Record

The PCP record routes card backup files to disk pack. The master of the disk pack family, named BACKUP, must not be restricted.

If you use more than one of the punch backup routing records, the system uses the following priority order to route the files: disk pack and disk.

USE PCRM Record

The PCRM record indicates that the location and contents of the first control card and each DATA(B) card is to be displayed as they are processed from pseudo card decks. This record provides data used primarily with the CONTROL option of the RN system command.

USE PRN Record

The PRN record directs the printer file to the printer.

USE QWIK Record

The QWIK record indicates that user program overlays are to be stored and retrieved from a memory buffer pool, a feature that is managed by a module named QWIK.

When an overlay request is made, the MCP checks the buffer pool for the requested overlay. If the MCP finds the overlay, the MCP transfers the overlay from the buffer into the overlay area of the program. If MCP does not find the overlay in the buffer pool, the MCP retrieves the overlay from disk and copies it into the buffer. If the overlay is used again, the MCP retrieves it from the buffer.

The size of the buffer pool is set by the LIMIT QWIKPOOL record.

USE RJE Record

The RJE record indicates that an RJE handler is to be executed when a remote job entry (RJE) station becomes active.

USE RMOV Record

The RMOV record automatically resolves duplicate file conditions on disk or disk pack by indicating that the old file is to be removed.

If you use the USE LIB record, the system displays the message “DUP LIB REMOVED” to confirm that a file has been deleted. If you do not use the USE LIB record, no message is displayed.

USE RTSL Record

The RTSL record indicates that short- or long-tape-block read operations that are not multiples of the logical record size are to be treated as I/O errors, unless the program using the file indicates otherwise.

USE SCHM Record

The SCHM record indicates that a message is to be displayed each time a program is scheduled for execution.

USE SNAP Record

The SNAP record enables SNAP, a useful debugging tool that captures the state of the memory when certain processor errors occur. When you use the SNAP record, a certain amount of memory is reserved for the SNAP picture.

USE STGO Record

The STGO record displays a message when an executing program is stopped by an ST command, a STOP command, or a crash-out mechanism. If memory is needed, STGO rolls out the file and also informs you when the program is brought back into memory.

USE STOQ Record

The STOQ record indicates that the system can use the storage queue method of interprogram communication.

USE SYST Record

The SYST record causes a module to be loaded into memory in order to run the software package named Functional and Logical Analysis of Machine Efficiency (FLAME) that monitors system performance.

USE SYUP Record

The SYUP record executes a program named SYSUP after a cold-start or a halt/load. The SYSUP program is a user-written program that performs site-specific functions, such as starting up the various programs that comprise the normal operating environment.

The bound version of the SYSUP program causes the MCP to perform a DMPALL (ZIP 0 DM MIX <mix number>) before going to EOJ. If the system fails, the mix number is the number of the job being worked on at the point of system failure. Refer to Volume 3 for additional information about the SYSUP program.

USE TERM Record

The TERM record causes programs that encounter irrecoverable errors to be terminated. Otherwise, you must terminate the job yourself by using the DS or DP system commands.

USE THLT Record

The THLT record halts the processing of a task and displays a fault screen if the system encounters MCP errors. The fault screen gives you the option to continue processing the task or to perform a halt/load for the MCP. If you do not use the USE THLT record, the task is terminated automatically.

USE TIME Record

The TIME record requires that the time be entered before a cold-start or a halt/load is completed.

However, automatic emergency halt/loads performed because of the USE AUHL record do not require that the time be entered.

USE TPLB Record

The TPLB record causes a message to be displayed each time a tape file is made available.

USE TPMK Record

The TPMK record indicates that any tape containing a nonrewound reel with a write-enable ring be saved in the event of a halt/load.

USE TPNO Record

The TPNO record indicates that each tape must have a serial number before the tape can be written to. A tape need not have a serial number to be read.

USE TRAK Record

The TRAK record causes a TRAK module to be loaded into memory and allocates a buffer for tracking information. For more information, refer to the discussion of the LIMIT TRAKBUFFER record.

USE TRMD Record

The TRMD record indicates that jobs that terminate abnormally are to be dumped, unless termination was due to a memory parity error.

If you use both the USE TRMD record and the USE TERM record, the USE TRMD record takes precedence.

USE WRKP Record

The WRKP record causes work files to be directed to unrestricted system resource disk packs.

USE ZIPM Record

The ZIPM record indicates that the following message is to be displayed each time a program passes an instruction to the MCP:

<job-id> ZIP <control information message>

Note: The START and STOP commands are not displayed when this record is used.

ssog1/commands/use.txt · Last modified: 2009/07/07 06:57 by scott
 
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki