ClearPath OS 2200 Series Release 13.2 Software Planning and ...

MSCP Changes
When you install MSCP, the following runstreams are added:
• MSCP (Run-id is MSCP)
• MSCPRT (Run-id is MSCPRT)
• MSCP/RT (Run-id is MSCPRT)
General Exec Considerations
If you choose to do a SOLAR installation of the separate MSCP product, the MSCP
program must first be terminated using the E keyin. The MSCP product is always
installed in the file SYS$LIB$*MSCP. The default install for MSCP is MODE A, which will
insert an @START,A/X of the realtime MSCPRT runstream into the AUTO$START
element in SYS$LIB$*RUN$. The customer can choose to SOLAR-install the nonrealtime
version of MSCP by specifying MODE B, which will insert an @START,A/X of
the non-realtime MSCP runstream into the AUTO$START element in SYS$LIB$*RUN$.
MSCP runstreams include MSCP, MSCPRT, and MSCP/RT. The runstreams MSCPRT
and MSCP/RT are identical and perform real-time enforcement of your monitor
programs.
The @START image for MSCP or MSCPRT is contained in element AUTO$START in
SYS$*RUN$ or SYS$LIB$*RUN$. The image should be updated with a site-acceptable
account number and quota set to let the MSCPRT run in the real-time environment.
By default, SYS$*RUN$.AUTO$START automatically starts the real-time version of the
MSCP product. If you choose to SOLAR-install this product, SOLAR creates a new entry
in SYS$LIB$*RUN$.AUTO$START to start the MSCP product. If @START statements for
MSCP exist in both of your AUTO$START elements, two different instances of the
MSCP background run will become active during every system reboot. Therefore, if you
choose to SOLAR-install this product, you should remove the @START statement for
MSCP/RT from SYS$*RUN$.AUTO$START so that the @START statement in
SYS$LIB$*RUN$.AUTO$START is the only one which gets used.
Refer to the Exec Administration Reference Manual for additional information.
4.1.4. ClearPath OS 2200 Release 12.0
This subsection describes the Exec migration and compatibility considerations that apply
to Exec level 48R4.
• Problems could occur after a site moves up to UDSC 16R1. At that point, if the
customer is running on CP11.2 EXEC level or higher, the customer could use UDSC
16R1 to create some of the new type nine QITEMs. Then, if they drop back to a
CP11.0 EXEC or earlier, they would need to have the cross-boot PLE (18390396)
applied to their CP11.0 or earlier EXEC level. The CP11.1 or higher EXEC will
recognize the type nine QITEMs but the CP11.0 EXEC will not unless the PLE is
added.
7831 0349–043 4–5