Installation Reference

This page provides detailed reference information shared by both the New Installation and Upgrade procedures.

INSTALL/SGS Direct Customization

The installation parameters (INSTALL/SGS) contain SGS statements used to generate the installation runstreams. These parameters are normally set through the interactive INSTALL procedure, so direct modification is seldom required.

Parameter Categories

The INSTALL/SGS contains two categories of parameters:

• Installation parameters — must be correct to properly install the LSAM. These must be set prior to generating installation runstreams.
• Run-time parameters — identify options during program execution. These are required for installation but may be altered without reinstalling.

Non-Standard BIS Background Error RIDs

Direct customization of the INSTALL/SGS is required when using a non-standard BIS Background Error Report location (other than 3B208/209). Modify the following SGS labels:

SGS Label	Parameter
ERRMODE	Cabinet (Mode)
ERRTYPE	Drawer (Type)
ERRRID	Report (RID)

When the Background Error RID format differs from the default, modify these SGS labels to match the field positions:

SGS Label	Parameter	Default Column
DATECOL	Starting column of the date	2
TIMECOL	Starting column of the time	9
USERCOL	Starting column of the user-id	31
STNCOL	Starting column of the station-id	48

Multiple LSAMs

Multiple LSAMs may be installed and used concurrently within the same OS 2200 image by using unique values for certain parameters.

Unique Installation Parameters

Each LSAM must have unique values for:

1. File Qualifier — the qualifier used for LSAM files
2. TIP File — both name and number
3. Common Data Bank (CDB) name — the installation procedure uses the file qualifier as part of the CDB name by default, ensuring uniqueness

Unique Configuration Parameters

Set with LSAMCFG/ECL, each LSAM must have unique values for:

4. CpComm/CMS PROCESS name — requires defining a unique PROCESS to CpComm/CMS for each LSAM
5. OpCon host machine name — must match the machine name defined in OpCon
6. Console reserved keyins — for the LSAM, LMAM, SMAJOR, and XFRTCP runs
7. Port Number — the LSAM communication port

LSAM System Files

The following files are created during the installation procedure. Each file's placement is specified during the File Placement Parameters step.

Core LSAM Files

LSAM-LOCK

• Used by: All OS 2200 installations
• Prevents concurrent executions of the LSAM.
• Required by the LSAM upon startup.
• This file remains empty.

SMAJOR-LOCK

• Used by: All OS 2200 installations
• Prevents concurrent executions of SMAJOR.
• Required by SMAJOR upon startup.
• This file remains empty.

SMAMSC-LOCK

• Used by: Installations utilizing the SMA Monitor Services Connector
• Prevents concurrent executions of SMAMSC.
• Required by SMAMSC upon startup.
• This file remains empty.

XFRTCP-LOCK

• Used by: All OS 2200 installations
• Prevents concurrent executions of XFRTCP.
• Required by XFRTCP upon startup.
• This file remains empty.

BKLSAM

• Used by: LSAM installations
• Contains log data from the LSAM.
• Cycled every day at midnight and whenever the BRKPT command is issued.
• The LSAM-RUN/ECL runstream catalogs and cycles this file upon startup.
• SMA recommends allowing the default 32 file cycles for 30 days of log entries.

BKSMAFTA

• Used by: All OS 2200 installations
• Contains log entries for SMA File Transfer jobs.

BKSMAJOR

• Used by: All OS 2200 installations
• Contains log entries generated by the SMAJOR runstream.
• The SMAJOR/ECL runstream catalogs and cycles this file each time it is used, every day at midnight, and whenever the BRKPT command is issued.
• SMA recommends allowing the default 32 file cycles for 30 days of log entries.

BKSMAMSC

• Used by: Installations utilizing the SMA Monitor Services Connector
• Contains log entries generated by the SMAMSC runstream.
• The SMAMSC/ECL runstream catalogs and cycles this file each time it is used, every day at midnight, and whenever the BRKPT command is issued.
• SMA recommends allowing the default 32 file cycles for 30 days of log entries.

BKXFRTCP

• Used by: All OS 2200 installations
• Contains log data from XFRTCP.
• Cycled each day at midnight and whenever the BRKPT command is issued.
• Cataloged and cycled by the XFRTCP/ECL runstream each time it is started.
• SMA recommends allowing the default 32 file cycles for 30 days of log entries.

BKXFRPRT

• Used by: All OS 2200 installations
• Contains the PRINT$ entries generated by the XFRPRT runstream.
• The XFRPRT/ECL runstream catalogs and cycles this file each time it is used.

DUMPCDB-PRT

• Used by: All OS 2200 installations
• Contains the printout (dump) of the non-configured common bank (NCCB) used for data exchange between LSAM modules.
• The DUMPCDB/ECL runstream catalogs and cycles this file each time it is used.

LSAMPARMBKP

• Used by: All OS 2200 installations
• Contains after-images of the LSAM configuration parameters when updated by LSAMCFG/ECL.
• Used by the LPARMRES/ECL procedure when restoring LSAM configuration parameters.

XFRPRT-PRT

• Used by: All OS 2200 installations
• Contains the printout (dump) of the TIP file used for LSAM configuration and communication.
• The XFRPRT/ECL runstream catalogs and cycles this file each time it is used.

BIS MAM/LMAM Files

The following files are created only when LMAM and BIS MAM are installed.

LMAM-LOCK

• Prevents concurrent executions of the LMAM.
• Required by the LMAM upon startup.
• This file remains empty.

SAM-MAM-LOCK

• Used by both the LMAM and the MAM to detect when the LMAM is processing.
• Required to be present when the LMAM is started.
• This file remains empty.

BKLMAM

• Contains log data from the LMAM.
• The LMAM-RUN/ECL runstream catalogs and cycles this file upon startup, every day at midnight, and whenever the BRKPT command is issued.
• SMA recommends allowing the default 32 file cycles for 30 days of log entries.

MAM-x-LOG

• Contains the day's MAM log data, ELT'd from RID 7 of MAM's data type.
• While MAM is processing, a new cycle is created every day at midnight and whenever the number of log entries exceeds 3000 lines.
• SMA recommends allowing the default 32 cycles for 30 days of log entries.

MAM-x-FINLOG

• Contains the day's MAMFIN entries, ELT'd from RID 8 of MAM's data type.
• While MAM is processing, a new cycle is created every day at midnight.
• This file remains empty when MAMFIN is not used for run termination status.

MAM-x-BACKUP

• Contains the MAM BIS RIDs when the run MAMBACKUP is executed.
• Also used to restore MAM BIS RIDs by MAMRESTORE.

Installing without the Non-Configured Common Bank

The non-configured common bank (NCCB) is required for JORS and OpCon File Transfer capabilities. For sites that do not need JORS or File Transfer and do not want the NCCB installed:

1. After setting the LSAM Qualifier (@QUAL) but before running @ADD *SKDPRG.INSTALL, enter:

@COPY,S *SKDPRG.COMPILE-SKEL/UPD-NO-CDB,*SKDPRG.COMPILE-SKEL/UPDATES

2. Continue the installation procedure with @ADD *SKDPRG.INSTALL.

Note

The Common Data Bank prompts will still appear during installation — you may accept the defaults. The INITIALIZE step will attempt to copy the common bank template to the SYS$ file. If that file is not present, an error will result. This is not a fatal error and the installation can continue.

Non-Common Banked Program Collection

For sites not using a program absolute starting address of 022000 for ACOB DML program collections, the following information is required when using a starting address of 01000. These prompts appear when you respond with 01000 to the "Enter COBOL I-Bank start address at your site" prompt during the INSTALL procedure.

Prompt	Description
Enter file name containing COBOL run time relocatables	Local file containing COBOL run time relocatable elements (default: SYS$LIB$*ACOB-CB)
Enter file name for COBOL run time program banks	File for storing COBOL run time banks. The default *SKDPRG file is released with the required banks.
Enter file name containing PCIOS run time relocatables	File containing PCIOS relocatables (default: PCIOS*PCIOS-REL)
Is PCIOS (C)ommon-banked or (N)on-banked?	C includes common-bank entry points for PCIOS. N collects PCIOS relocatables into the program absolute.
Create COBOL-BANKS elements?	N to use banks supplied in *SKDPRG. Y to recreate from the local COBOL library.
Enter file name containing SORT run time relocatables	File containing SORT relocatables (default: SYS$LIB$*SORT)
Enter file name containing UCSRTS run time relocatables	File containing UCSRTS relocatables (default: SYS$LIB$*UCSRTS)
Enter the file name containing the System Library (SYSLIB) relocatables	File containing system library routines (default: SYS$LIB$*SYSLIB)

After completing these prompts, continue with the remaining Compile/Collection Parameters.