Logon to your privileged usercode.

Start the Runtime WFL, by entering:

 START NGEN28/WFL/RUNTIME
 ("usercode","pack","aliaspack", 
FALSE, GCA media parameter  )

The usercode value is the usercode to which the Runtime is installed, which might be an asterisk (*).

The pack value is the family name of the pack to which the Runtime is installed, which might be DISK or altpack.

The aliaspack value is the pack for your station alias file. Refer to the Agile Business Suite Runtime for ClearPath MCP Administration Guide for more information on station aliases.

GCA media parameter = “MD=MediaDirectory MN=MediaName N=Cut#”

MediaDirectory is the directory containing the installation files:

EPSILON

(TRANSFER)GCA

ETA

(TRANSFER)ETA/GCA

MediaName is the name of the pack on which the installation files are located.

<Transfer pack>

Cut# is the cut number for the release.

1000-<nn>

For example:

“MD=(TRANSFER)ETA/GCA MN=TFRPACK N=1000-02”

License Agreement – Before the installation begins, you will be asked to accept the license agreement. The installation job is suspended twice to allow you to read the license information. The terms of the license agreement might be found in the instruction blocks. Enter ?<mix> IB nn from MARC to view each instruction block. Enter ?<mix>OK to accept the license agreement and install Agile Business Suite 7.0 for the MCP Operating System.

During the installation, you will be prompted:

 ** DO YOU WISH TO OVERWRITE EXISTING LIBRARIES (HUBROUTER, RATL, ETC.) WITH THE
 LIBRARIES IN THIS RELEASE?
 AX YES TO OVERWRITE OR AX NO TO INSTALL/RETAIN LATEST VERSION **

This allows you to overwrite existing libraries, even if their release level is higher than the GCA release.

Respond with AX YES to overwrite existing libraries.

Respond with AX NO to allow the installation job to use release checking and only install the new libraries if they have a higher release level than the existing libraries.

During the installation, you will be prompted to confirm the version of AB Suite 7.0 MCP Runtime that is being installed.

Respond with OK to confirm.

DS the job to terminate the installation.

During the installation, you will be prompted for the SSR level of the LOGIC and DUMPINFO files to be installed. The SSR level must match that of the DMALGOL compiler currently installed on your system. You will be prompted to respond to the waiting entry with one of the following:

EPSILON

581, 591, YES

ETA

591, YES

The meanings of these are:

If you respond with YES and your MCP release level is not supported, you will be prompted to enter the SSR level of a DMALGOL compiler that is installed on your system and is supported.

If the SSR level you have selected is not the SSR level of the default compilers, you are advised to modify the TASKSTRING attribute of NGEN28SYS/BLD with the location of the compilers after the IC installation is complete.

  WFL MODIFY (<Runtime Usercode>)NGEN28SYS/BLD ON <Runtime Pack>;
  TASKSTRING= "[Tparam,]<compiler list>";

Where <Tparam> is T=5.

Include this if you are installing the EPSILON package on a host with the ETA architecture.

Where <compiler list> is

  C=<COBOL85 compiler>, D=<DMALGOL compiler>, B=<BINDER>

For example,

  WFL MODIFY (RTUSER)NGEN28SYS/BLD ON RTPACK;
  TASKSTRING= "T=5, C=*COBOL85/591, D=*DMALGOL/591, B=*BINDER/591";

or

WFL MODIFY (RTUSER)NGEN28SYS/BLD ON RTPACK;
TASKSTRING= "C=(MYUSER)COBOL85/600 ON MYPACK,
D=(MYUSER)DMALGOL/591 ON MYPACK, B=(MYUSER)BINDER/591 ON MYPACK";

During the installation, you will be prompted for the SSR level of the SMU, DMU and CFG codefiles to be installed. The SSR level must match that of the DMSII level of the application databases that are built by the runtime being upgraded. You will be asked to respond to the waiting entry with one of the following:

EPSILON

581, 591, YES

ETA

591, YES

The meanings of these are:

If you respond with YES and your MCP release level is not supported, you will be asked to enter a supported level of DMSII that is installed your machine.

If the systems that are deployed by this runtime environment use DMSII software located under a usercode and on a pack, as specified by DMSII Usercode and DMSII pack segment configuration properties in the configuration of the segment, the SSR level selected for SMU, DMU, and CFG should correspond to the SSR level of the DMSII software.

If there are AB Suite application databases of different DMSII release levels, some use 58.1 and some use 59.1, for example, it is strongly recommended that separate runtime environments should be created to handle the different levels. Designate one runtime for SSR 58.1 and one for SSR 59.1.

During the installation, you might be prompted to acknowledge that an updated version of MLSLIBRARY has been installed. Respond to the waiting entry with OK. If you use a language other than ENGLISH, check for untranslated messages in the file

NGEN28/MLSLIBRARY/UNTRANSLATED.

During the installation, you will be asked whether you wish to install Application Builder.

You will be asked “DO WISH TO INSTALL APPL_BLD? AX YES/NO”. You have the choice of installing the default Application Builder or a clone. If you wish to install either, respond with ?<mix#> AX YES, otherwise respond with ?<mix#>AX NO.

If you respond with YES, you will then be asked “DO YOU WISH TO INSTALL CUSTOM OR DEFAULT APPL_BLD? AX C FOR CUSTOM OR D FOR DEFAULT”.

Installing Application Builder with Default Identity

Respond with ?<mix#>AX D if you wish to install the default Application Builder. This creates/modifies APPL_BLD_70.

Installing Application Builder with Custom Identity

To install Application Builder with Custom identity, you need the following details:

Respond with ?<mix#>AX C, if you wish to install a custom version of MCP Builder Server. Next, a message appears,

“PLEASE ENTER IDENTITY AND PORT NUMBER TO BE USED WITH CUSTOM APPL_BLD”.

You are then prompted to enter the identity for the custom APPL_BLD:

“AX IDENTITY TO BE USED WITH CUSTOM APPL_BLD (MAX 6 CHARS)”

Respond with ?<mix#>AX <identity>

Next, you are prompted to enter the port number for the custom APPL_BLD:

“AX PORT NUMBER TO BE USED WITH CUSTOM APPL_BLD”

Respond with ?<mix#>AX <port number>

After entering the identity and port number, you are asked to confirm what you entered:

“FOR CUSTOM APPL_BLD YOU ENTERED: ID=<identity>, PORT=<port>,

IS THIS CORRECT? AX YES OR NO”

If it is correct, respond with ?<mix#>AX YES, otherwise respond with ?<mix#>AX NO and enter them again.

After Installing Application Builder

Check for waiting entries in the mix. You might need to respond to a request to initialize the APPL_BLD files. Respond to the initialization request with one of the following:

During the installation, you will be asked whether you wish to install RATL, LRSS, and TPTOMARC. If you wish to install either of them, respond with ?<mix>AX YES, otherwise respond with ?<mix>AX NO.

If you have installed an update to RATL during the installation, you must disable and enable RATLPCM to activate the new server.

  NA CCF DISABLE PCM RATLPCM
  NA CCF ENABLE PCM RATLPCM

Set up the required Support Libraries (SLs).

If you did not start the Runtime install job with adequate privileges for the SLs to be done automatically, set up the required Support Libraries (SLs) now.

If your host has Security Administrator (SECADMIN) status enforced, sign on to MARC with a SECADMIN status usercode. (Only a user/task/job with SECADMIN status might issue SL commands when SECADMIN status is enforced.)

From MARC, enter:

  SL NGEN28SERVICES = *NGEN28/1/LIBRARY ON altpack
  SL EXAMINERLIB = *EXAMINER/LIBRARY ON altpack

The altpack gives the alternate pack for the family of the usercode under which you are running Runtime. For example, your usercode family might be specified as follows:

  DISK = INTPACK OTHERWISE SYSPACK

If so, enter SYSPACK as your altpack value.

Configuration of Runtime is complete. For your next steps, refer to Configuring COMS for Applications.