Features of LINC Generate - Public Support Login - Unisys
Features of LINC Generate - Public Support Login - Unisys
Features of LINC Generate - Public Support Login - Unisys
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
New <strong>Features</strong> for MCP Based <strong>LINC</strong> Systems<br />
See your DMS II Utilities Options Guide for guidelines on deciding whether it is more<br />
efficient to rebuild the set or subset from the data set, or to rebuild from the set or subset<br />
itself.<br />
Correct Calculation <strong>of</strong> Blocksize<br />
In <strong>LINC</strong> II Releases 16.1 and 16.2, blocksizes were calculated incorrectly for some<br />
structures, and were different to the sizes shown on the DASDL Options (CDLA) screen in<br />
<strong>LINC</strong> <strong>Generate</strong>.<br />
In <strong>LINC</strong> Release 16.3, blocksizes are calculated correctly. Structures affected are those<br />
that are a half byte less than a multiple <strong>of</strong> 6 bytes (for example, 17.5 and 23.5 bytes) and<br />
that have defaults set on their DASDL Options screen.<br />
Note: This change may lead to unexpected reorganizations <strong>of</strong> your <strong>LINC</strong> Databases<br />
after migration.<br />
Avoiding reorganization<br />
To avoid reorganizations due to blocksize changes:<br />
1. Open the file system/SOURCE/DMS.<br />
2. Identify the structures that are affected by this change.<br />
Look at the trailer records which contain the record lengths. The trailer record begins<br />
with %%%%%TRAILER, and the record length is in a 6 digit field at position 39. This<br />
field includes one decimal, so that the value 000175 indicates a record <strong>of</strong> length <strong>of</strong><br />
17.5 bytes (which would be affected).<br />
3. Access the DASDL Options screen in <strong>LINC</strong> <strong>Generate</strong>.<br />
4. For each structure you identified in Step 2, enter the blocksize value from <strong>LINC</strong> II<br />
Releases 16.1 or 16.2.<br />
You can now generate your <strong>LINC</strong> System.<br />
Use <strong>of</strong> Connection Libraries for HUB<br />
Prior to <strong>LINC</strong> Release 16.3, default timeout values were used to detect client or server<br />
program failure for HUB (external Automatic Entry) transactions.<br />
In <strong>LINC</strong> Release 16.3, the HUB facility uses the Connection Library system s<strong>of</strong>tware<br />
feature, which enables the establishment <strong>of</strong> a two-way interface with calling <strong>LINC</strong><br />
Systems. This can lead to improved response. In addition, an abort <strong>of</strong> any attached<br />
program is detected, enabling immediate transaction aborting or recovery procedures<br />
(depending on the transaction status <strong>of</strong> the particular program that aborted).<br />
1-8 v