18.08.2013 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

5.9. COMUS<br />

COMUS<br />

COMUS is used to build products. Although COMUS installation functionality is still<br />

supported in the current release, SOLAR has replaced COMUS as the installation tool for<br />

all products.<br />

General Considerations<br />

• COMUS supports keyed product generation <strong>and</strong> keyed product installation.<br />

• COMUS supports compressed <strong>and</strong> uncompressed 1/2-inch cartridge tapes. The<br />

COMUS comm<strong>and</strong>s that accept <strong>and</strong> support 1/2-inch tape compression values are<br />

INSTALL, REGISTER, <strong>and</strong> BUILD.<br />

• Products installed with SOLAR do not update the COMUS database. Be sure to use<br />

SOLAR reports to list the installed levels of these products, rather than the COMUS<br />

system installation logs.<br />

• Continue to use COMUS to build all symbolic products. Build information for<br />

products installed with SOLAR is contained in an ASCII file for each product on the<br />

package tape for that product.<br />

• The LIBSAVE <strong>and</strong> LIBLOAD runstreams are no longer released with COMUS. The<br />

runstreams are included with SOLAR, <strong>and</strong> will continue to be released in<br />

SYS$*RUN$ on the Exec boot tape.<br />

• The use of large program files (LPF) to build products is restricted.<br />

• Do not specify the maintenance update levels of products in BUILD comm<strong>and</strong>s (for<br />

example, use xR1 instead of xR1A).<br />

• If you have any local or third-party products that are COMUS installable, consider the<br />

following:<br />

− COMUS does not support initiation of installation runstreams in dem<strong>and</strong> mode<br />

with the @ADD statement. You can either start the runstream during the install<br />

session or enter the @START statement to initiate the runstreams.<br />

− If there is a cycle limit on SYS$*DATA$, SYS$LIB$*RUN$, or<br />

SYS$LIB$*PROC$, your installation might fail. COMUS <strong>and</strong> SOLAR create a +1<br />

cycle of these files, which could cause a mass storage hold (M-hold) if the cycle<br />

number tries to exceed the maximum. You are advised not to use cycle limits for<br />

these files.<br />

Refer to the COMUS End Use Reference Manual for detailed information regarding<br />

product generation with COMUS.<br />

<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 12.0<br />

COMUS Level 6R9<br />

Compatibility<br />

The following products either use the st<strong>and</strong>ard build routine (CB$STD$BUILD) provided<br />

by COMUS <strong>and</strong> st<strong>and</strong>ard build skeletons (SKL-LDSVCTRL <strong>and</strong> SKL-LOADSAVE) or have<br />

updated their product-specific build routines <strong>and</strong> skeletons in <strong>Release</strong> 12.0. These<br />

products fully support the COMUS buffered-write <strong>and</strong> pool-id feature for the BUILD<br />

comm<strong>and</strong>.<br />

7831 0349–043 5–13

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!