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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Checkpoint/Restart (CKRS)<br />

Migration<br />

The <strong>OS</strong> <strong>2200</strong> Cryptographic Library (CryptoLib) must be installed for Cipher API to run.<br />

Previous levels of Cipher API did not require CryptoLib.<br />

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

Java applications can access Cipher API by using the st<strong>and</strong>ard Java Cryptography<br />

Architecture (JCA) classes <strong>and</strong> interfaces. Cipher API h<strong>and</strong>les cryptographic requests<br />

through a cryptographic service provider called UnisysJCE.<br />

In addition to the API <strong>and</strong> Java Cryptographic Service Provider support, Cipher API<br />

includes a comm<strong>and</strong> line utility for file encryption.<br />

5.5. Checkpoint/Restart (CKRS)<br />

General Considerations<br />

• Because CKRS saves a particular environment <strong>and</strong> then restores that exact saved<br />

environment, any changes to the hardware or software environment (such as a<br />

change in mass storage device or installation of a new product level) between the<br />

taking of the checkpoint <strong>and</strong> the attempted restart might prevent successful restart.<br />

• For a successful restart, the Exec <strong>and</strong> CKRS product levels must be compatible<br />

(specifically, they must be from the same system release level).<br />

• A checkpoint <strong>and</strong> subsequent restart will be unpredictable if you change addresses<br />

or data in a common bank between the checkpoint <strong>and</strong> the restart. The linked<br />

(resolved) references in the program are no longer valid <strong>and</strong> the restarted program<br />

would refer to incorrect addresses <strong>and</strong> data. Also, a checkpoint request is not<br />

fulfilled <strong>and</strong> a fatal checkpoint error results if any write-enabled common banks are<br />

based at the time a checkpoint request is made.<br />

5.6. COMAPI<br />

General Considerations<br />

• The security attributes for subsystem User-id, ACRs, <strong>and</strong> files are changed. The<br />

following attributes are required:<br />

− The clearance level attributes for COMAPI are minimum=0 <strong>and</strong> maximum=63.<br />

− The compartment set applies only to Security Level 2 or higher.<br />

− The value is access to ALL compartments, even if no compartments are defined.<br />

− Trusted privileges are SSBAFC, SSBYCOMP, SSBYPASSOWNR, <strong>and</strong> SSCCL.<br />

• If your application is designed to use socket function calls, you must include the<br />

library element SYS$LIB$*COMAPI$LIB.SOCKET$LIB in the link of your application.<br />

Refer to the COMAPI User Guide for more information.<br />

If you use a newer level of the socket library in your application <strong>and</strong> subsequently try<br />

to run on an older level of COMAPI, it will not work. You must re-link with the socket<br />

library that is installed for that level of COMAPI.<br />

Note: You can use old socket libraries with newer levels of COMAPI.<br />

5–4 7831 0349–043

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

Saved successfully!

Ooh no, something went wrong!