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.12. DPS<br />

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

DPS Level 6R5A<br />

Compatibility<br />

DPS<br />

When using a version of DPS 6R5A, users must generate new CONNECTER working<br />

storage/message format for every DPS screen previously generated <strong>and</strong> used with DPS<br />

6R5, <strong>and</strong> import the resulting COBOL structures into their ePortal Developer projects<br />

using the import wizard. Otherwise, a mismatch with the message/record format results<br />

in the DPS run-time system generating errors on transaction input, or ePortal receiving<br />

unrecognizable data on transaction output.<br />

CONNECTOR working storage/message format for DPS 6R5A now contains data fields<br />

for DPS screen number, DPS screen name, DPS form library filename, CONNECTOR<br />

working storage version number (1), <strong>and</strong> selected DPS screen control information.<br />

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

DPS Level 6R5<br />

Compatibility<br />

For DPS Level 6R5, when you define or use a field for use with ePortal/TIP Connector<br />

terminal type, only the A, C, I, L, N, O, X, <strong>and</strong> S minor field types are supported. The B,<br />

D, <strong>and</strong> R minor field types are restricted. Using B, D, <strong>and</strong> R minor field types in your DPS<br />

form for use with ePortal/TIP Connector yields unpredictable results.<br />

For DPS Level 6R5, the messages transmitted between ePortal <strong>and</strong> the TIP/DPS<br />

transactions have an additional 8-character field preceding the entire message. This field<br />

contains the DPS screen name, which is used by ePortal as the discriminator field.<br />

Transactions or Initial Control Programs (ICPs) which may intercept the transaction input<br />

message prior to being processed by the DPS run-time system must be cognizant of the<br />

new field.<br />

5.13. Distributed Data Processing File <strong>and</strong> Job<br />

Transfer (DDP-FJT)<br />

General Considerations<br />

• You must install DDP-PPC before you build or execute DDP-FJT.<br />

• You must install I18NLIB to execute DDP-FJT. This is necessary because DDP-FJT<br />

uses ELMS, which, in turn, requires I18NLIB.<br />

• The Print Driver <strong>and</strong> Print Manager components of DDP-FJT are no longer supported<br />

because PERCON has been discontinued.<br />

• DDP-FJT background runs error on a system running Fundamental Security<br />

(SENTRY=0).<br />

• DDP-FJT requires that IRU be installed with mode FSAH or ALTFSAH.<br />

7831 0349–043 5–17

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

Saved successfully!

Ooh no, something went wrong!