ClearPath Enterprise Servers MCP Release DCL - Public Support ...

ClearPath Enterprise Servers 

ClearPath MCP 

Documentation Changes List (DCL) 

ClearPath MCP 13.0 

April 2010 6875 9497–003 

unisys 

imagine it. done.

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information 

described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to 

purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the 

products described in this document are set forth in such agreement. Unisys cannot accept any financial or other 

responsibility that may be the result of your use of the information in this document or software material, including 

direct, special, or consequential damages. 

You should be very careful to ensure that the use of this information and/or software material complies with the 

laws, rules, and regulations of the jurisdictions with respect to which it is used. 

The information contained herein is subject to change without notice. Revisions may be issued to advise of such 

changes and/or additions. 

Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed 

at private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard 

commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract 

data rights clauses. 

Unisys and ClearPath are registered trademarks of Unisys Corporation in the United States and other countries. 

All other brands and products referenced in this document are acknowledged to be the trademarks or registered 

trademarks of their respective holders.

Contents 

Documentation Changes List ........................................................................... 1 

ALGOL ....................................................................................................................... 1 

Component: ALGOL PRI-11426492 ............................................... 1 

Manual Corrections For CNV_FORMATTTIME 

And CNV_FORMATTIMETMP ........................................... 1 


BEGINSEGMENT And Nested Procedure 

Clarification .......................................... 1 


REMOVEFILE Statement Fails When Using 

Long File Names ................................................................. 2 

Component: ALGOL PRI-11520286 .............................................. 2 

CHANGEFILE Statement Fails When Using 

Long File Names ................................................................. 3 


$SET LI_SUFFIX = PROCEDURE Implemented ................. 4 


$SET LI_SUFFIX = PROCEDURE Implemented ................. 5 

Component: DMALGOL PRI-11467563 ....................................... 5 

A 'BEGIN Statement Should Include a 'END ..................... 5 

Component: DMALGOL PRI-11489184........................................ 5 

DMS LOCK/MODIFY NOWAIT Enhancement .................. 5 

Component: DMALGOL PRI-11519814 ........................................ 6 

DMS SECURE NOWAIT Enhancement ............................... 6 

ASSISTANT.............................................................................................................. 7 

Component: ASSISTANT PRI-11472061 ...................................... 7 

RUN and START With Accesscode .................................... 7 

Component: ASSISTANT PRI-11472745 ...................................... 7 


Component: ASSISTCOMPILER PRI-11472044 ......................... 8 


Component: PROPERTIES PRI-11472036 ................................... 9 


Component: TOOLS PRI-11472052 .............................................. 9 


BCMANAGER ....................................................................................................... 10 

Component: DR PRI-11535879 .................................................... 10 

Add Support for Local Recovery Hosts .......................... 10 

Component: DR PRI-11539831 ..................................................... 12 

Support Recovery of Several Hosts by One 

DR Host ................................................................................ 12 

Component: DR PRI-11540490.................................................... 13 

Add Support for Local Recovery Hosts .......................... 13 

6875 9497–003 iii

Contents 

C 15 

Component: DR PRI-11541909 .................................................... 14 

Support Recovery of Several Hosts by One 

DR Host ............................................................................... 14 

Component: C PRI-11448780 ....................................................... 15 

Default Promotions Apply to Variable Length 

Argument Lists ................................................................. 15 

CANDE .................................................................................................................... 16 

Component: CANDE PRI-11475795 ............................................ 16 

Implement LI ODT Command ............................................ 16 


Count Incorrect Accesspassword Against 

SECOPT LOGONATTEMPTS .......................................... 19 


COMPILE AS $ Replaces 

Source File .......................................................................... 19 


Add ARCHIVE, CATALOG, MODIFY, And 

MKDIR Verbs ..................................................................... 20 


Add ARCHIVE, CATALOG, MODIFY, And 

MKDIR Verbs ..................................................................... 20 

Component: CANDE PRI-11543839 ........................................... 20 

COMPILE AS $ Replaces 

Source File .......................................................................... 20 


Explain "CANDE SERVICE UNAVAILABLE" 

Message ............................................................................. 20 

Component: CANDE PRI-11568386............................................ 22 

Explain "CANDE SERVICE UNAVAILABLE" 

Message ............................................................................. 22 

CENTRALSUPP ..................................................................................................... 22 

Component: CCSFILE PRI-11494871 .......................................... 22 

Changes To Mappings Involving EBCDICUTL ................ 22 

Component: CCSFILE PRI-11539483 .......................................... 23 


Component: CENTRALSUPPORT PRI-11525687 ..................... 24 


Component: CENTRALSUPPORT PRI-11539475 ..................... 25 


CLEARPATHEPORTAL ........................................................................................ 27 

Component: MCP PRI-11437923 ................................................. 27 

ePortal Software Installation During Cold 

Start ..................................................................................... 27 

COBOL74 ............................................................................................................... 27 

Component: COBOL74 PRI-11452272 ....................................... 27 

Condition-Name With THRU Not Syntaxed 

When Not Ascending ...................................................... 27 


ERROR 357 Is Misleading .................................................... 28 


ERROR 357 Is Misleading .................................................... 29 

iv 6875 9497–003

Contents 

COBOL85 ............................................................................................................... 30 


Condition-Name With THRU Not Syntaxed 

When Not Ascending ...................................................... 30 


Only Last $LI_SUFFIX Is Applied ........................................ 31 


Unlimited Nesting Of $INCLUDE Can Loop 

Forever ................................................................................ 31 


DMS LOCK/MODIFY NOWAIT Enhancement ................ 32 


DMS LOCK/MODIFY NOWAIT Enhancement ................ 32 

Component: COBOL85 PRI-11496008....................................... 33 

Procedure Division Header (Change) 

Documentation Is Incorrect ........................................... 33 


Migration Issue with COBOL85 COMMON 

Clause .................................................................................. 33 


Migrating From COBOL68 Where This 

Program Compiles Okay With COBOL74 ................... 34 


$INCLUDEd Lines In A COPY Get LISTed 

Unconditionally .................................................................. 35 


DMS SECURE NOWAIT Enhancement ............................. 36 


DMS SECURE NOWAIT Enhancement ............................. 36 


Array Parameter Passed To COMS Service 

Function .............................................................................. 37 


Document OCCURS Maximum Limit ............................... 38 


Document OCCURS Maximum Limit ............................... 38 


Document Bindinfo Difference Between 

COBOL74 And COBOL85 ............................................... 38 


Document Bindinfo Difference Between 

COBOL74 And COBOL85 ............................................... 39 


File Status "04" Is Not Implemented................................. 40 


File Status "04" Is Not Implemented................................. 43 

COMS ..................................................................................................................... 45 

Component: COMS PRI-11551599 .............................................. 45 

Delete Unused Stations And Associated 

Hosts ................................................................................... 45 


6875 9497–003 v

Contents 


Hosts ................................................................................... 46 

Component: COMS PRI-11560733 ............................................. 47 

Disabling Programs When Program Fails To 

Initiate .................................................................................. 47 



Initiate .................................................................................. 49 

Component: PAF PRI-11555098 .................................................. 51 

Session Language is Ignored When Using 

The Update Command .................................................... 51 

Component: PAF PRI-11555101 ................................................... 51 

Session Language is Ignored When Using 

The Update Command .................................................... 51 

Component: UTILITY PRI-11447988 ........................................... 52 

Utility Refresh Command Must Be 

Uppercased And Not Abbreviated .............................. 52 



Hosts ................................................................................... 52 



Hosts ................................................................................... 53 



Initiate .................................................................................. 55 



Initiate .................................................................................. 56 

COMTI .................................................................................................................... 58 

Component: COMTI PRI-11583041 ............................................. 58 

Connector PSH Help Command ........................................ 58 

Component: COMTI PRI-11583059 ............................................ 58 

Connector PSH Help Command ........................................ 58 

DBCERTIFICATION .............................................................................................. 58 

Component: DBCERTIFICATION PRI-11507344 ...................... 58 

Invalid Syntax Using CERTIFY ALL With Set 

Name ................................................................................... 58 

DMSII ...................................................................................................................... 59 

Component: ACR PRI-11428100 .................................................. 59 

Correctly Handling TranStamp/RSN For 

Overflow Situation ........................................................... 59 

Component: ACR PRI-11499899 ................................................. 60 

Allow To Set The Memory Resident For All 

Sets To Coarse .................................................................. 60 

Component: ACR PRI-11540830 ................................................. 61 


Sets To Coarse .................................................................. 61 

Component: AUDITLIB PRI-11462553 ....................................... 63 

Correct Logic for Sequential Read Audit 

While in Use by DB .......................................................... 63 

Component: COPYAUDIT PRI-11419500 ................................... 64 

vi 6875 9497–003

Contents 

Document Tapeset Errors In Utilities 

Operations Guide ............................................................. 64 

Component: COPYAUDIT PRI-11444857 .................................. 65 

OVERRIDE Option For QUICKCOPY From 

Tape/Tapeset To DISK .................................................... 65 

Component: DASDL PRI-11498779 ............................................ 66 


Sets To Coarse .................................................................. 66 

Component: DASDL PRI-11540856 ............................................ 67 


Sets To Coarse .................................................................. 67 

Component: PROPERTIES PRI-11499902 ................................. 68 


Sets To Coarse .................................................................. 68 

Component: PROPERTIES PRI-11540864 ................................. 70 


Sets To Coarse .................................................................. 70 

Component: UTILITY PRI-11590021 .............................................71 

Problems with SYSTEM/DMDUMPDIR 

Documentation ..................................................................71 

DMSQL ................................................................................................................... 72 

Component: DMSQL PRI-11428908 ........................................... 72 

Some of the documented NA commands are 

not supported by DMSQL. ............................................. 72 

Component: DMSQL PRI-11450504 .......................................... 72 

Modify Documentation for Database Update 

Requirements .................................................................... 73 

Component: RDC PRI-11410596 .................................................. 73 

Modify SQL Database Text Addition Needed 

for Relational Design Center. ........................................ 73 

DSS .......................................................................................................................... 74 

Component: LIO PRI-11498060 ................................................... 74 

Deimplement FTAM Attributes ......................................... 74 

Component: NFT PRI-11441670 .................................................. 75 

Minor Improvements to NFT .............................................. 75 

DUMPALL .............................................................................................................. 75 

Component: DUMPALL PRI-11498051 ...................................... 75 

Deimplement FTAM Attributes ......................................... 75 

DUMPANALYZER ................................................................................................ 77 

Component: DUMPANALYZER PRI-11266371 ......................... 77 

Update ASDNUMBER Command ...................................... 77 


Introduce Options To The LINKCHECK 

Command ........................................................................... 80 

Component: DUMPANALYZER PRI-11433464 ........................ 81 

Introduce New SUMMARY Option Of 

LANGUAGE......................................................................... 81 


Convert Code Address Into Sequence 

Number ............................................................................... 82 


6875 9497–003 vii

Contents 

Convert Code Address Into Sequence 

Number ............................................................................... 85 


PBTUNLOAD Option To Unload Single-File 

Printer Backup Tape ........................................................ 88 


Analyze Coremap File Without Memory 

Dump ................................................................................... 89 


ACTUALMYNAME File Attribute ....................................... 90 


FIB Command Now Supports An ALL Stacks 

Option .................................................................................. 90 


Improvements to PORT analysis ...................................... 91 


Analyze MEMRQ For A Given IOP .................................... 92 


System Factors (SF) Command ......................................... 93 


System Factors (SF) Command ......................................... 94 


Add SSL Logical IO Attributes and Errors ....................... 94 


Add SSL Logical IO Attributes and Errors ....................... 99 

Component: DUMPANALYZER PRI-11566987 ...................... 105 

Introduce New SUMMARY Option Of 

LANGUAGE....................................................................... 105 

Component: DUMPANALYZER PRI-11568785 ...................... 105 

New Commands And Options For Memory 

Pool Diagnostics ............................................................. 105 

Component: DUMPANALYZER PRI-11568807 .......................114 

New Commands And Options For Memory 

Pool Diagnostics ..............................................................114 

Component: DUMPANALYZER PRI-11570071 ....................... 123 

FIB Command Now Supports An ALL Stacks 

Option ................................................................................ 123 

EDITOR ................................................................................................................. 124 

Component: MACROS PRI-11517811 ....................................... 124 

Add New Macros For Dumpanalyzer 

Commands ....................................................................... 124 

Component: MACROS PRI-11537731....................................... 124 

Add New Macros For Dumpanalyzer 

Commands ....................................................................... 124 

EMAIL ................................................................................................................... 125 

Component: EMAIL PRI-11483704 ........................................... 125 

Clarify Server Specification in 

*INSTALLATION/OPTIONS File ................................... 125 

FILECOPY ............................................................................................................. 126 

Component: FILECOPY PRI-11409458..................................... 126 

JOBNAME Conflicts With ENCRYPT .............................. 126 

Component: FILECOPY PRI-11419305 ..................................... 126 

viii 6875 9497–003

Contents 

INCLUDE FILEKIND Produces Incorrect 

Results .............................................................................. 126 


Exclusion Of Files Which Are In-Use ............................. 127 


DENSITY Description Contains Extraneous 

Text .................................................................................... 129 


DENSITY Description Contains Extraneous 

Text .................................................................................... 129 

FILEDATA ............................................................................................................. 129 

Component: FILEDATA PRI-11428967 ..................................... 129 

DECK Modifier in COPYDECK Request.......................... 129 


Database Level Information ............................................. 130 

Component: FILEDATA PRI-11441025 ...................................... 131 

Using CANDE U to Run FILEDATA Gets an 

Error Report ...................................................................... 131 


FILEDATA Reports PROTECTED File Attribute ............ 132 

Component: FILEDATA PRI-11498078..................................... 132 

Deimplement FTAM Attributes ....................................... 132 

FTP ......................................................................................................................... 132 

Component: FTPSUPPORT PRI-11541348 .............................. 132 

Allow Directory COPY and Multi-File 

Command ......................................................................... 132 

Component: FTPSUPPORT PRI-11541356 .............................. 140 

Allow Directory COPY and Multi-File 

Command ......................................................................... 140 

INFOACCESS ....................................................................................................... 147 

Component: INFOACCESS PRI-11456189 ............................... 147 

Modify Documentation regarding support for 

Windows .......................................................................... 147 

JDBCFORMCP-TYPE4 ...................................................................................... 148 

Component: JDBCFORMCP-TYPE4 PRI-11392164 ............... 148 

JDBC Connection String Not Supporting the 

IPV6 HOSTNAMENAME ................................................ 148 

JRAC ..................................................................................................................... 149 

Component: JRAC PRI-11566839 ............................................. 149 

java.net.BindException - Address already in 

use: JVM_Bind ................................................................. 149 


java.net.BindException - Address already in 

use: JVM_Bind ................................................................. 152 

Component: JRAC PRI-11580041.............................................. 154 

Annotation Information ...................................................... 154 


Annotation Information ...................................................... 160 


New Product Name ............................................................ 165 

Component: JRAC PRI-11590101 .............................................. 165 

New Product Name ............................................................ 165 

6875 9497–003 ix

Contents 

KEYEDIOII ............................................................................................................ 165 

Component: KEYEDIOII PRI-11537138 ..................................... 166 

Clarification to the Setting of NORECOVERY 

Attribute ............................................................................ 166 

LICENSECENTER ................................................................................................ 167 

Component: LICENSECENTER PRI-11428894 ........................ 167 

Comparison Between Keys Files .................................... 167 

Component: LICENSECENTER PRI-11502130 ......................... 167 

License Center Help Update for 12.1 ERD .................... 167 

Component: LICENSECENTER PRI-11504272 ........................ 167 

Add x64 Support ................................................................. 167 

Component: LICENSECENTER PRI-11505813 ......................... 167 

License Center Help Update for 12.1 ERD .................... 167 

Component: LICENSESUPPORT PRI-11485278 ..................... 168 

Allow Progress Interrogation for Nightly 

Detail Delete Task .......................................................... 168 

Component: LICENSESUPPORT PRI-11486177 ..................... 168 

Allow Progress Interrogation for Nightly 

Detail Delete Task .......................................................... 168 

LOAD-UTILS ........................................................................................................ 168 

Component: LOADER PRI-11469027 ....................................... 168 


Printer Backup Tape ...................................................... 168 

LOG-TOOLS ........................................................................................................ 169 

Component: JOBFORMATTER PRI-11437877 ....................... 169 

System Option ENABLEPOSIX is 

Deimplemented .............................................................. 169 


Remove Support For LDML .............................................. 169 





Override Operator RSVP During RY and SV of 

CPM ................................................................................... 170 


New SYSOPS LMCDMULTIVOLUME and 

HLWAITFAMINDEX ........................................................ 170 

Component: JOBFORMATTER PRI-11475141 ........................ 170 

Daily Warning of Imminent Key Expiry .......................... 170 


Allow Comment With REMOTEUSER 

Definition .......................................................................... 173 


Audit Changes to System Maintained 

Usercode Attributes ...................................................... 175 


Documentation for RBAC Logging ................................. 176 


New Security Option SECURECOMM............................ 179 



x 6875 9497–003

Contents 


DMS Logging ........................................................................ 180 


DMS Logging ......................................................................... 181 

Component: JOBFORMATTER PRI-11591817 ......................... 181 

Log Inquire Permission Failures ....................................... 181 

Component: LOGANALYZER PRI-11444261 ........................... 182 

Allow More FIND Targets ................................................. 182 

Component: LOGANALYZER PRI-11445942 .......................... 183 

Allow Filtering On More Than One Usercode ............. 183 


Allow Selection of INSTALLATION Log 

Records ............................................................................. 184 


TRUNCATE Option Limits Number of Lines 

Per Entry ........................................................................... 184 


Analysis & Description of CIA Dialog and 

Node Records ................................................................. 185 


Update System Commands Allowed With 

OPERATOR Option ......................................................... 186 


Add PIO to Diagnostics Options ..................................... 187 





Log Enhancements for Workload 

Management ................................................................... 189 



Management ................................................................... 190 

Component: LOGANALYZER PRI-11521959 ............................ 191 

Documentation for RBAC Logging .................................. 191 


System Info returns information about 

networking data path interface .................................. 194 

Component: LOGANALYZER PRI-11554792........................... 195 



MARC ................................................................................................................... 195 

Component: MARC PRI-11469051 ............................................ 195 



Component: MARC PRI-11469060 ........................................... 195 







6875 9497–003 xi

Contents 






Component: MARC PRI-11517137 ............................................. 197 

DNOTE: Some Log Specs Missing In MARC's 

LOGGING Command Display ....................................... 197 

MCP ...................................................................................................................... 198 

Component: ATTABLEGEN PRI-11464521 .............................. 198 

Add SSL Logical IO Attributes and Errors ..................... 198 

Component: CCTABLEGEN PRI-11417213 ............................... 203 

Emit Warning If Predefined Word is Used ................... 203 

Component: CCTABLEGEN PRI-11487301 ............................. 204 

Implement STARTTIME With Day of Week ................ 204 

Component: CHECKPOINT PRI-11503608 .............................. 206 

Improve CHECKPOINT and RESTART 

Messages ......................................................................... 206 

Component: CONFIGURATION PRI-11413854 ....................... 210 


Component: CONFIGURATION PRI-11445225 ...................... 210 


Component: CONTROLLER PRI-11437711 .............................. 210 



Component: CONTROLLER PRI-11448577 ............................. 210 

Y Response Shows Long 

Tape Operations In Progress ...................................... 210 

Component: CONTROLLER PRI-11458980 .............................. 211 

Show Dates in Long Format in SQ Response .............. 211 

Component: CONTROLLER PRI-11459251 ............................... 211 

Allow FIND and SHOW to Use Relation 

For String Attributes ....................................................... 211 

Component: CONTROLLER PRI-11469795 ............................. 212 

Override Operator RSVP During RY and SV of 

CPM ................................................................................... 212 

Component: DATACOM PRI-11445624 .................................. 212 

Revise documentation for MAXPSEUDO 

value limit ......................................................................... 212 

Component: DISKFILES PRI-11384293 .................................... 213 

CHANGE and REMOVE Statements Return 

Result Information ......................................................... 213 


Message RES12 Now Includes a File Name ................. 215 

Component: DISKFILES PRI-11469191 ..................................... 218 

Improve "FILE REMOVED" Messages ............................ 218 







xii 6875 9497–003

Contents 


FILEDATA Reports PROTECTED File Attribute ............ 219 


NOLABEL Option for PG PK .............................................. 219 


Fix Disk File Header Message .......................................... 220 


Fix Disk File Header Message .......................................... 221 


GETSTATUS Miscellaneous Subtype 21 May 

Hang System ................................................................... 221 


Halt Load May Hang Waiting for JOBDESC 

File ...................................................................................... 222 


Halt Load May Hang Waiting for JOBDESC 

File ...................................................................................... 223 


NOLABEL Option for PG PK .............................................. 223 

Component: DMSII PRI-11582630 ............................................ 224 

DMS Logging ........................................................................ 224 


DMS Logging ........................................................................ 225 


Fix DMSII Log Records ...................................................... 226 


Fix DMSII Log Records ...................................................... 226 

Component: GETSTATUS PRI-11418210.................................. 228 

Old Getstatus/Setstatus Mix Requests ........................ 228 

Component: GETSTATUS PRI-11560229 ................................. 228 

GETSTATUS Miscellaneous Subtype 21 May 

Hang System ................................................................... 228 

Component: KEYS PRI-11474357 ............................................. 228 


Component: LIBMAINT PRI-11411240 ..................................... 231 

Improve NFT Messages .................................................... 231 


Warning 186 for Task Attributes SW6 and 

SW7.................................................................................... 233 


Minor Improvements to NFT ............................................ 235 

Component: LIBMAINT PRI-11447678 .................................... 235 

Improve Library/Maintenance Error Message ............. 236 


Generate Warning When File Marked 

Restricted During UNWRAP ........................................ 236 


Correct Description of Libmaint Tapes ......................... 237 

Component: LIBMAINT PRI-11474845 .................................... 238 

Locking KEYEDIOII Files ..................................................... 238 

Component: LIBRARIES PRI-11480993 ................................... 239 

Implement LI ODT Command .......................................... 239 

6875 9497–003 xiii

Contents 

Component: LOGGING PRI-11487581 ...................................... 242 

LOGGING MINIMAL and LOGGING DEFAULT 

Values ................................................................................ 242 

Component: LOGGING PRI-11515169 .......................................243 


Management ...................................................................243 

Component: LOGGING PRI-11522009 ..................................... 244 

Documentation for RBAC Logging ................................ 244 

Component: LOGGING PRI-11542883 .....................................246 

All Logging is in Version 1 Format ................................... 247 

Component: LOGGING PRI-11545653 ..................................... 247 

All Logging is in Version 1 Format ................................... 247 

Component: LOGICALIO PRI-11469001 ................................... 247 



Component: LOGICALIO PRI-11498043 .................................. 247 

Deimplement FTAM Attributes ....................................... 247 

Component: LOGICALIO PRI-11505228 ................................. 248 

Improve Tape Error Messages ....................................... 248 

Component: LOGICALIO PRI-11511660 ................................... 252 

Error Messages for READALABEL ................................. 252 

Component: LOGTABLEGEN PRI-11545904 .......................... 253 

Retrieve Log Descriptions ................................................ 253 

Component: LOGTABLEGEN PRI-11545939 .......................... 256 


Component: MAINTENANCE PRI-11485201 ........................... 258 

Cannot Reinitialize MCPESRSUPPORT Library 

Without Halt/Load .......................................................... 258 

Component: MEMORYMGMT PRI-11563775 ........................ 259 

Memory Pools D-Note For CU System 

Command ......................................................................... 259 

Component: MEMORYMGMT PRI-11564771......................... 261 

Memory Pools D-Note For CU System 

Command ......................................................................... 261 

Component: MESSAGES PRI-11459692 ..................................264 

Allow Message Suppression by Job Name .................264 

Component: MESSAGES PRI-11495109 .................................. 265 

Improve MCP MLS Messages ......................................... 265 

Component: MESSAGES PRI-11501117 .................................... 265 

Improve MLS Messages ................................................... 265 

Component: NETWORKING PRI-11552871 ............................. 266 



Component: NETWORKING PRI-11554008 ............................ 266 



Component: PHYSICALIO-DISK PRI-11487769 ..................... 267 

Update Critical Unit Definition .......................................... 267 

Component: PORTS PRI-11493912 ........................................... 268 

ACTUALMYNAME File Attribute ..................................... 268 

Component: PROC-METERING PRI-11473865 ...................... 268 

xiv 6875 9497–003

Contents 

Allow Multiple E-OPTIONS Records In 

*METER/EMAIL/DESTINATIONS ................................. 268 

Component: SCTABLEGEN PRI-11437869.............................. 270 



Component: SCTABLEGEN PRI-11469019 .............................. 271 









Component: SECURITY PRI-11476228 .................................... 276 


Definition .......................................................................... 276 


Privileged Processes Can Access Guarded 

Files .................................................................................... 277 








Component: SYSTEMSTATUS PRI-11532373 ........................ 280 

Remove Fine Priority From SYSTEMSTATUS 

Mix Requests .................................................................. 280 






Memory Pools D-Note For SYSTEMSTATUS 

Manual ............................................................................... 285 

Component: SYSTEMSTATUS PRI-11561578......................... 287 

Memory Pools D-Note For SYSTEMSTATUS 

Manual ............................................................................... 287 

Component: TASKING PRI-11430562 ......................................289 

Remove IO Interrupt Strategy Value ..............................289 

Component: TASKING PRI-11441963 ...................................... 291 

PROCESSINFO Task Attribute .......................................... 291 

Component: TASKING PRI-11486843 ...................................... 292 

HISTORY_TEXT Interface in MCPSUPPORT 

Library ................................................................................ 292 

Component: UNASSIGNED PRI-11449034 ............................ 294 

Remove Code Segment Halt Feature ........................... 294 

Component: UNASSIGNED PRI-11547826 .............................. 295 

Libra 780/790 Documentation .......................................... 295 

Component: UNASSIGNED PRI-11547834 ............................. 295 

6875 9497–003 xv

Contents 

Libra 780/790 Documentation .......................................... 295 

Component: UTILITIES PRI-11472672 ...................................... 295 

Export Procedure GETMYCODEFILEHEADER .............. 295 

Component: UTILITIES PRI-11481060 ...................................... 296 

Export Procedure 

GETMYCODEFILEHEADER_STAR ............................... 296 

Component: UTILITIES PRI-11507204 ......................................298 

ASERIES_INFO Reports PROTECTION, 

PROTECTIONVALUE ......................................................298 

MCPJAVA ............................................................................................................298 

Component: INFRASTRUCTURE PRI-11465692 ....................298 

Add support for control key-ins ......................................298 

Component: INFRASTRUCTURE PRI-11485481 .................... 299 

Disable editing the device number value in 

JavaConfig ........................................................................ 299 

Component: INFRASTRUCTURE PRI-11486894 .................... 299 

Add Pseudo DNS names for EVLAN 

endpoints. ........................................................................ 300 

Component: INFRASTRUCTURE PRI-11538789 ................... 300 

Set Windows recovery options for the Java 

Monitor service.............................................................. 300 

Component: INFRASTRUCTURE PRI-11538797 ................... 300 

Set Windows recovery options for the Java 

Monitor service.............................................................. 300 

Component: JAVAIO PRI-11594476 ......................................... 301 

Allow FILEEQUATE on new JAVA files to 

expand their size ............................................................ 301 


Allow FILEEQUATE on new JAVA files to 

expand their size ............................................................ 302 


INTNAME can only contain Characters, 

numbers, hypen, underscore ...................................... 302 

Component: JAVAPROXY PRI-11543260 ............................... 302 

Exitcodes 129-150 are usually valid values, 

not negative ..................................................................... 302 

Component: JAVAPROXY PRI-11559948 .............................. 304 

Exitcodes 129-150 are usually valid values, 

not negative .................................................................... 304 

Component: JAVAPROXY PRI-11574629 ................................305 

Add ARGS file to proxy to allow for MANY 

Java parameters .............................................................305 

Component: JAVAPROXY PRI-11578322 ................................ 307 

Add ARGS file to proxy to allow for MANY 

Java parameters ............................................................. 307 

Component: JNI PRI-11459331 ................................................. 308 

Enable JNI Support for user-written code. ................. 308 

Component: JNI PRI-11459684 ................................................ 308 

Enable JNI Support for user-written code. ................. 308 

Component: MCPJAVA PRI-11462006 ................................... 308 

Mechanism to allow STDOUT/STDERR 

remote output to PAUSE ............................................ 308 

xvi 6875 9497–003

Contents 

MCP-WORKLOADMGR .................................................................................. 309 

Component: WLMSUPPORT PRI-11551963 .......................... 309 

Increase Allowed Statistics File Retention 

Period ............................................................................... 309 

Component: WLMSUPPORT PRI-11551971 ............................ 310 

Increase Allowed Statistics File Retention 

Period ................................................................................ 310 

Component: WORKLOADCENTER PRI-11413196 ................. 310 

Implementation Of Process Monitor ............................. 310 

Component: WORKLOADCENTER PRI-11458793 ................ 310 

Clarify Privilege Requirements to Use 

Workload Center ............................................................ 310 

Component: WORKLOADCENTER PRI-11475167 .................. 311 

Client Tracing Capabilities .................................................. 311 


Support For Binary Statistics File Format ..................... 312 




Configuration Dialog For Client Tracing ......................... 312 

Component: WORKLOADCENTER PRI-11535895 ................ 312 

LOAD/CONFIGURATION/PARAMETERS/RES 

ULT ..................................................................................... 312 


Descriptive error messages for missing 

configuration parameters files. .................................. 313 

MESSAGESUPPORT .......................................................................................... 313 

Component: MESSAGESUPPORT PRI-11459706 .................. 313 

Allow Message Suppression by Job Name ................. 313 

MQMCP ............................................................................................................... 315 

Component: API PRI-11431992 .................................................. 315 

Implement Use of the WinRPC Client Fast 

Interface ............................................................................ 315 

NEWP ................................................................................................................... 315 

Component: NEWP PRI-11426671 ............................................ 315 

Remove 2's Complement (INT32) Types ...................... 315 


Documentation Unclear for Array Dimension 

Subtype Mismatch ......................................................... 315 


GETINDEX and GETELEMENTSIZE Intrinsics ................ 316 


GETINDEX and GETELEMENTSIZE Intrinsics ................ 316 

NX/COMSCENTER ............................................................................................. 316 

Component: COMSCENTER PRI-11563031 ............................ 316 

Implement the the COMS Update Command 

and Pass Command ....................................................... 316 

Component: COMSCENTER PRI-11563058 ............................ 317 

Implement the the COMS Update Command 

and Pass Command ....................................................... 317 

Component: NX/COMSCENTER PRI-11554377 ..................... 317 

6875 9497–003 xvii

Contents 

Allow Selected Stations In Station Search 

Form To Be Copied ........................................................ 317 


Allow Selected Stations In Station Search 

Form To Be Copied ........................................................ 318 


Station Search With Empty Copy Text 

Causes Run-Time Error 381 ......................................... 319 


Station Search With Empty Copy Text 

Causes Run-Time Error 381 ......................................... 319 

NX/DBCENTER ................................................................................................... 319 

Component: DBCSERVICES PRI-11456014 ............................. 319 

Database Operations Center Does Not 

Create Log File for Active NX Server ........................ 319 

NX/EDIT ................................................................................................................ 320 

Component: NXEDIT-CLIENT PRI-11484875 .......................... 320 

Load XREF File Option Added Under Xrefs In 

The Popup Menu ............................................................ 320 

Component: NXEDIT-CLIENT PRI-11500021 ........................... 320 

Add Startcase As Edit Menu Item .................................. 320 

Component: NXEDIT-CLIENT PRI-11508502 .......................... 321 

Recently Listed Files As File Menu Item ....................... 321 

Component: NXEDIT-CLIENT PRI-11512062 ........................... 321 

Accesscode Password Must Be All 

Uppercase ........................................................................ 322 

Component: NXEDITSUPPORT PRI-11438784 ...................... 322 

Support Connect as Logged On User ............................ 322 

NX/OPCENTER ....................................................................................................324 

Component: CLIENT PRI-11424651 ..........................................324 

Maximum Number Of Fields For A View Is 

Not Documented ............................................................324 

Component: CLIENT PRI-11502776 ..........................................324 

Display And RSVP Message Appears On 

Every View Definition ....................................................324 

NX/SERVICES ......................................................................................................324 

Component: ADMIN-CLIENT PRI-11487211 ............................324 

Admincenter Client Truncates Long Share 

Names ...............................................................................324 

Component: LAUNCHER PRI-11495460 .................................. 326 

Procedure To Run Launcher As An 

Application At System Boot ........................................ 326 

Component: LAUNCHER PRI-11538304 .................................. 328 

Procedure To Run Launcher As An 

Application At System Boot ........................................ 328 

Component: MCP-NEIGHBORHOOD PRI-11492398 ............ 329 


Component: MCP-NEIGHBORHOOD PRI-11552188 ........... 330 

MCP Neighborhood Icon Is Visible Under 

Network Node Of Win7 Explorer .............................. 330 

Component: MCP-NEIGHBORHOOD PRI-11554172 ............ 330 

xviii 6875 9497–003

Contents 

MCP Neighborhood Icon Is Visible Under 

Network Node Of Win7 Explorer .............................. 330 

Component: PCDRIVER PRI-11547729 .................................... 331 

Share Names With Embedded Blanks Not 

Accessible ........................................................................ 331 

Component: PCDRIVER PRI-11547753 .................................... 331 

Share Names With Embedded Blanks Not 

Accessible ........................................................................ 331 

OLEDB .................................................................................................................. 332 

Component: OLEDBPROVIDER PRI-11591027 ....................... 332 

Accented characters in EBCDIC database .................... 332 

Component: OLEDBPROVIDER PRI-11591043 ......................333 

Accented characters in EBCDIC database ....................333 

PASCAL ............................................................................................................... 334 

Component: PASCAL PRI-11433901 ....................................... 334 

Fix Heap OVERFLOW Result To Be 29, not 2 ............. 334 


Fix Heap OVERFLOW Result To Be 29, not 2 ............. 334 


Increase Maximum Value of $HEAPSIZE ..................... 336 


No Bounds Checking On Parameters ........................... 336 

PDIR ..................................................................................................................... 336 

Component: PDIR PRI-11436234 ............................................. 336 

Return Information Through TASKSTRING 

Attribute ........................................................................... 336 

Component: PDIR PRI-11476775 .............................................. 337 

Allow Multiple Attributes in TASKSTRING 

List ...................................................................................... 337 

Component: PDIR PRI-11507212 .............................................. 338 

ASERIES_INFO Reports PROTECTION, 

PROTECTIONVALUE ..................................................... 338 

PRINTS ................................................................................................................ 339 

Component: DEPCON PRI-11580521 ....................................... 339 

Configure OPEN_TRY_COUNT for Virtual 

Server ............................................................................... 339 

Component: DEPCON PRI-11580548 ...................................... 339 

Configure OPEN_TRY_COUNT for Virtual 

Server ............................................................................... 339 

Component: PRINTDRIVERS PRI-11484042 .......................... 340 

Allow Suppression of Form Feed After File is 

Printed .............................................................................. 340 


Implement Test IOHandler .............................................. 340 


Allow Background Image For Generated 

HTML Document ........................................................... 340 

Component: PRINTDRIVERS PRI-11524044 ........................... 341 

Implement USEREQUESTNAME option ........................ 341 


Implement MYIPADDRESS option in 

MCPPRT and TCPDIRECTPRINTER ............................ 341 

6875 9497–003 xix

Contents 


Implement REQUIRESTSTATUS option in 

MCPPRT ............................................................................ 341 

Component: PRINTDRIVERS PRI-11563783 ...........................342 

Allow STREAMFILE I/O Handler to Generate 

Read-only Output Files .................................................342 

Component: PRINTDRIVERS PRI-11563791 ............................342 

Allow STREAMFILE I/O Handler to Generate 

Read-only Output Files .................................................342 



Printed .............................................................................. 343 

Component: PRINTS PRI-11447198 ......................................... 344 

Expand Maximum Number of Requests from 

28339 to 100000 ............................................................ 344 



28339 to 100000 ............................................................ 344 

Component: PRINTS PRI-11464033 ........................................ 344 

Allow Printing Of Files Exceeding 16777215 

Lines .................................................................................. 344 

Component: PRINTS PRI-11464441......................................... 344 

Allow Printpartial With Files Exceeding 

16777214 Lines ............................................................... 344 



Printed .............................................................................. 345 

Component: PRINTS PRI-11551513 .......................................... 345 

Add A New Aseries Info Attribute to Return 

DL BACKUP Familyname ............................................. 345 


Add A New Aseries Info Attribute to Return 

DL BACKUP Familyname ............................................. 345 



Printed .............................................................................. 346 



Printed .............................................................................. 346 

Component: PRINTS PRI-11567363......................................... 346 


Printed .............................................................................. 346 

Component: REPRINTS PRI-11447210 .....................................347 


28339 to 100000 .............................................................347 

SAN-DATAMOVER ............................................................................................347 

Component: WINSERVICES PRI-11479529 .............................347 

TCP/IP transfers from Windows to MCP are 

now supported. ..............................................................347 


xx 6875 9497–003

Contents 

SAN DATAMOVER SUPPORTS MCP TO 

WINDOWS TO WINDOWS VIA DISK AND 

TCP/IP ................................................................................347 

Component: WINSERVICES PRI-11539904 ........................... 348 

SAN DATAMOVER SUPPORTS SSL FILE 

TRANSFERS .................................................................... 348 


SAN DATAMOVER SUPPORTS SSL FILE 

TRANSFERS .....................................................................350 

Component: WINSERVICES PRI-11546064 ............................350 

DATAMOVER SUPPORTS SECURE FTP 

TRANSMISSIONS ...........................................................350 

SDASUPPORT.....................................................................................................350 

Component: SDASUPPORT-NONDA PRI-11445951 ............350 

Allow Filtering On More Than One Usercode .............350 

SECURITY ............................................................................................................ 352 

Component: MAKEUSER PRI-11476210 .................................. 352 


Definition .......................................................................... 352 

Component: MAKEUSER PRI-11478883 .................................353 

Interactive Output Scrolls Too Fast ................................353 

Component: MCPCRYPTOAPI PRI-11518702 ........................ 354 

Fix Description Of 

McpCertGetX509EncodedCertificateChain ............ 354 

Component: MCPCRYPTOAPI PRI-11519229 ......................... 355 


McpCertGetX509EncodedCertificateChain ............. 355 

Component: MCPCRYPTOAPI PRI-11519253 .........................356 


McpCertGetX509EncodedCertificateChain .............356 

SECURITYCENTER .............................................................................................356 

Component: CLIENT PRI-11573291 ...........................................356 

Implement export and import of IPsec 

policies ..............................................................................356 

Component: CLIENT PRI-11576010 .......................................... 359 


policies ............................................................................. 359 

Component: CRYPTOMANAGER PRI-11539017 ................... 361 

DNOTE for JAVA Stores feature in 

SecurityCenter (part of FN #1947). ............................ 361 

Component: CRYPTOMANAGER PRI-11539033 ................... 367 

DNOTE for JAVA Stores feature in 

SecurityCenter (part of FN #1947). ............................ 367 

Component: INSTALLATION PRI-11493106 ........................... 373 


Component: RBACSUPPORT PRI-11533388 .......................... 373 

Documentation for RBAC Logging ................................. 373 

Component: RBACSUPPORT PRI-11591833 .......................... 376 

Log Inquire Permission Failures ...................................... 376 

Component: SYSTEMPOLICY PRI-11479944 ......................... 377 


policies .............................................................................. 377 

6875 9497–003 xxi

Contents 


Implement testing of IPsec policies within 

the View & Update Wizards. ....................................... 379 


Implement testing of IPsec policies within 

the View & Update Wizards. ....................................... 379 

Component: SYSTEMPOLICY PRI-11538941 .......................... 379 


policies .............................................................................. 379 


DNOTE for ADD/IPSEC/TESTING/WIZARD 

(Feature 1935, 1st half). ................................................. 382 

Component: SYSTEMPOLICY PRI-11556744 ........................ 388 

DNOTE for ADD/IPSEC/TESTING/WIZARD 

(Feature 1935, 1st half). ................................................ 388 

Component: USERCENTER PRI-11506879 ............................. 393 


Usercode Attributes ..................................................... 394 

SLICE .................................................................................................................... 395 

Component: ALL PRI-11534813 ................................................ 395 

$OPTIMIZE Has No Affect On $BOUNDS .................... 395 

Component: COBOL85 PRI-11438741 .................................... 395 

COBOL85 Epilog Procedure In Host Program 

Is Allowed ....................................................................... 395 


New STERNWARN CCI For 

Deimplementation Warning ....................................... 396 


New STERNWARN CCI For 

Deimplementation Warning ........................................ 397 

Component: COBOL85 PRI-11490379 ..................................... 397 

DMS LOCK/MODIFY NOWAIT Enhancement .............. 397 


DMS LOCK/MODIFY NOWAIT Enhancement ............. 399 

Component: COBOL85 PRI-11520171 ..................................... 399 

DMS SECURE NOWAIT Enhancement .......................... 399 


DMS SECURE NOWAIT Enhancement .......................... 400 

SORT ..................................................................................................................... 401 

Component: SORT PRI-11351387 ............................................. 401 

Generate Syntax Errors For Invalid Numeric 

Sort Key Lengths ............................................................ 401 

Component: SORT PRI-11538754 ............................................ 402 

Generate Syntax Errors For Invalid Numeric 

Sort Key Lengths ........................................................... 402 

TADS .................................................................................................................... 403 

Component: TADS PRI-11438211 ............................................. 403 

BYE In Multitasking Environment Could 

Cause DS of Subordinate Task .................................. 403 

TELNET ................................................................................................................ 403 

Component: TELNETSUPPORT PRI-11567967...................... 403 

xxii 6875 9497–003

Contents 

Support Telnet Sessions Connected over 

SSL .................................................................................... 403 

Component: TELNETSUPPORT PRI-11576605 ..................... 404 

Support Telnet Sessions Connected over 

SSL .................................................................................... 404 

WFL ...................................................................................................................... 405 

Component: WFL PRI-11417132 ............................................... 405 

Emit Warning If Predefined Word is Used .................. 405 

Component: WFL PRI-11417868 .............................................. 405 

WARNSUPPRESS Option Now Available ..................... 405 


Give MCP Deimplementation Messages 

While Parsing Task Attributes ................................... 406 


CHANGE and REMOVE Statements Return 

Result Information ........................................................ 406 


Extend Maximum String Length to 1800 

Characters ....................................................................... 408 


Add TIMEDATE(HHMMSSPPPP) ..................................... 408 


Allow Nested INCLUDE Files ........................................... 409 


Add TIMEDATE(YYYYMMDDHHMMSSPPPP) ............ 409 


WARNSUPPRESS Option Now Available ...................... 410 

Component: WFL PRI-11471331 .................................................411 

Catch Invalid Hostname Error ...........................................411 

Component: WFL PRI-11478174 ................................................411 

START AND WAIT Still Waits When Used in 

PROCESS Statement ......................................................411 


Catch Invalid Hostname Error .......................................... 413 


Implement STARTTIME With Day of Week ................. 413 


Implement STARTTIME With Day of Week ................. 416 

Component: WFL PRI-11512356 ................................................ 418 

Assigned to YOURNAME Is 

Documented Incorrectly .............................................. 418 

WINMQ ................................................................................................................ 419 

Component: API PRI-11432239 ................................................. 419 

Implement Use of the WinRPC Client Fast 

Interface ............................................................................ 419 

Component: API PRI-11442447 ................................................. 419 

Update "Selecting the RPC Server" Section 

Within the Documentation ........................................... 419 

Component: API PRI-11442471 .................................................. 421 

Fix WinMQ API Support Library RPC Reason 

Codes Within Documentation ..................................... 421 

WIN-RPC ..............................................................................................................425 

6875 9497–003 xxiii

Contents 

Component: EIDL PRI-11433812................................................425 

Remove Client Fast Interface Key ..................................425 

Component: RPC PRI-11433499 ............................................... 427 

Remove Client Fast Interface Key .................................. 427 

Component: RPC PRI-11433758 ............................................... 428 

Remove Client Fast Interface Key ................................. 428 

Component: RPC PRI-11449298 .............................................. 430 

Allow User To Stop/Start Endpoint Mapper 

Server ............................................................................... 430 

Component: RPC PRI-11458661 ................................................ 431 

Allow User To Stop/Start Endpoint Mapper 

Server ................................................................................ 431 

xxiv 6875 9497–003

Documentation Changes List 

ALGOL 

Component: ALGOL PRI-11426492 

Manual Corrections For CNV_FORMATTTIME And 

CNV_FORMATTIMETMP 

SYMPTOMS: 

Examples under CNV_FORMATTTIME and CNV_FORMATTIMETMP in the Algol 

Programming Reference Manual, Volume 1 are giving wrong results. 

RESOLUTION COMMENTS/DOCUMENTATION NOTES (D-NOTES): 

In the ALGOL Programming Reference Manual, Volume 1: Basic 

Implementation (8600 0098-507); Section 10, Internationalization; 

Procedure Descriptions; CNV_FORMATTIME (page 10-59) update the 

following in the example: 

Replace TIME_ARY[0:9] with TIME_ARY[0:5]. 

In the same section under CNV_FORMATTIMETMP (page 10-61) update the 

following in the example: 

Replace TIME_ARY[0:9] with TIME_ARY[0:5]. 


BEGINSEGMENT And Nested Procedure 

Clarification 

SYMPTOMS: 

When the BEGINSEGMENT Compiler Control Option is used in a 

procedure before any variables have been declared for that 

procedure then the 

compile may fail with the error message: 

6875 9497–003 1


A PROCEDURE MAY NOT BE SPLIT ACROSS SEGMENTS. 

This error message is caused by confusion as to if the procedure 

being declared is going to be included in the new user segment. 

If no variables are declared in the procedure before the 

BEGINSEGMENT option is used, then the procedure is NOT included in 

the new user 

segment. 

If a variable is declared in the procedure before the BEGINSEGMENT 

option is used, then the procedure is included in the new user 

segment. 

This functionality could be made clearer in the documentation. 



Implementation (8600 0098-508); Section 7. Compiling Programs; 

Compiler Control Options; Option Descriptions; BEGINSEGMENT Option 

add the following text to the end of the second paragraph that 

begins "The BEGINSEGMENT option must appear": 

If the BEGINSEGMENT option is used within a procedure 

declaration, then it must be specified after at least one 

declaration within 

that procedure. 

That is, it must be in the . 


REMOVEFILE Statement Fails When Using Long File Names 

SYMPTOMS: 

The REMOVEFILE statement fails when attempting to remove a file 

with more than 12 nodes in the LFILENAME. Consider the below 

test case, on execution the B2 := REMOVEFILE (FN2); statement 

returns a non zero value indicating the failure and we can verify 

the same using FILE command, 

BEGIN 

REAL R2; 

BOOLEAN B2; 

EBCDIC ARRAY FN2[0:255]; 

FILE F2; 

REPLACE FN2[0] BY "01/02/03/04/05/06/07/08/09/10/11/12/13."; 

REPLACE F2.LFILENAME BY FN2; 

F2.FILEUSE := VALUE(OUT); 

F2.NEWFILE := TRUE; 

F2.KIND := VALUE(DISK); 

R2 := OPEN (F2); 

CLOSE (F2, LOCK); 

DISPLAY (FN2); 

B2 := REMOVEFILE (FN2); 

2 6875 9497–003

DISPLAY (STRING(REAL(B2.[39:20]),*)); 

END. 

Sample output; 

#RUNNING 99887 

#9988 DISPLAY:01/02/03/04/05/06/07/08/09/10/11/12/13.. 

#9988 DISPLAY:10. 

#ET=0.1 PT=0.0 IO=0.0 

FILE 01 :S 

01/02/03/04/05/06/07/08/09/10/11/12/13 DATA 




Implementation (8600 0098-508); Section 4. Statements; 

REMOVEFILE Statement; Directory Element; add the following 

text after the fourth paragraph, 

To remove files that contain long file name nodes please refer to 

the REMOVELFILE procedure in the System Software Utilities 

Operations Reference Manual. 


CHANGEFILE Statement Fails When Using Long File Names 

SYMPTOMS: 

The CHANGEFILE statement fails when attempting to change a file 

with more than 12 nodes in the LFILENAME. Consider the below 

test case, on execution the CHANGEFILE statement returns a non zero 

value indicating the failure and we can verify the same using FILE 

command, 

BEGIN 

REAL R2; 

BOOLEAN B2; 

EBCDIC ARRAY FN2[0:255]; 

FILE F2; 

REPLACE FN2[0] BY "01/02/03/04/05/06/07/08/09/10/11/12/13."; 

REPLACE F2.LFILENAME BY FN2; 

F2.FILEUSE := VALUE(OUT); 

F2.NEWFILE := TRUE; 

F2.KIND := VALUE(DISK); 

R2 := OPEN (F2); 

CLOSE (F2, LOCK); 

DISPLAY (FN2); 

B2 := CHANGEFILE (FN2,"11/12/13/14/15/16/17/18/19/20/21/22/23."); 

DISPLAY (STRING(REAL(B2.[39:20]),*)); 

END. 

6875 9497–003 3


Sample output : 

5570 PK17087 (SWAMYR)01/02/03/04/05/06/07/08/09/10/11/12/13 

REPLACED 

5570 DISPLAY:01/02/03/04/05/06/07/08/09/10/11/12/13.. 

5570 DISPLAY:10. 

FILE 11 :S 

#NO MATCHING FILES FOUND 



Implementation (8600 0098-508); Section 4. Statements; 

CHANGEFILE Statement; Directory Element; add the following 

text after the last paragraph "In the CHANGEFILE statement.... 

...on which the files reside.", 

To change a filename that contains long file name nodes please 

refer to the CHANGELFILE procedure in the System Software Utilities 

Operations Reference Manual. 


$SET LI_SUFFIX = PROCEDURE Implemented 

SYMPTOMS: 

There should be a way for the lineinfo to be set to the name of the 

procedure where the sequence number occurs. 


When the user adds $SET LI_SUFFIX = PROCEDURE to their program, the 

lineinfo will be modified to be an underscore followed by the name 

of the procedure. 

For example: 

#7877 DIVIDE BY ZERO @ (00000500_PROC3) 

#F-DS @ 00000500_PROC3, 00022000. 

The ALGOL Programming Reference Manual, Vol. 1 should be modified 

as follows: 

In Section 7. Compiling Programs; Compiler Control Options; Option 

Descriptions; LI_SUFFIX Option: 

Change the RailRoad diagram to the following: 

-- LI_SUFFIX ------------- ---------| 

| | | | 

-- = -- --- PROCEDURE --------| 

Add the following paragraph between the first and second paragraphs 

in the explanation text: 

PROCEDURE appends an underscore and the procedure name to the 

4 6875 9497–003


sequence number in the LINEINFO information. It takes effect 

with the next procedure that is seen. The procedure name is 

truncated if it is larger than 35 characters. 


$SET LI_SUFFIX = PROCEDURE Implemented 

SYMPTOMS: 

There should be a way for the lineinfo to be set to the name of the 

procedure where the sequence number occurs. 


When the user adds $SET LI_SUFFIX = PROCEDURE to their program, the 

lineinfo will be modified to be an underscore followed by the name 

of the procedure. 

For example: 

#7877 DIVIDE BY ZERO @ (00000500_PROC3) 

#F-DS @ 00000500_PROC3, 00022000. 

The ALGOL Programming Reference Manual, Vol. 1 should be modified 

as follows: 

In Section 7. Compiling Programs; Compiler Control Options; Option 

Descriptions; LI_SUFFIX Option: 

Change the RailRoad diagram to the following: 

-- LI_SUFFIX ------------- ---------| 

| | | | 

-- = -- --- PROCEDURE --------| 

Add the following paragraph between the first and second 

paragraphs in the explanation text: 

PROCEDURE appends an underscore and the procedure name to the 

sequence number in the LINEINFO information. It takes effect 

with the next procedure that is seen. The procedure name is 

truncated if it is larger than 35 characters. 

Component: DMALGOL PRI-11467563 

A 'BEGIN Statement Should Include a 'END 

SYMPTOMS: 

A Compile-Time BEGIN statement has the syntax: 

-- 'BEGIN ---- 'END -- 

After 'BEGIN is seen, if the end of the program is seen during the 

processing of the , then no message is given 

that the 'END was expected but not seen. 

6875 9497–003 5



If 'END is not seen while processing a Compile-Time BEGIN 

statement, the compiler now issues the warning: 

WARNING:PREPROCESSOR END STATEMENT EXPECTED BUT NOT SEEN. 


DMS LOCK/MODIFY NOWAIT Enhancement 

SYMPTOMS: 

A new NOWAIT option has been added to the BDMS LOCK/MODIFY 

statement. The NOWAIT option provides a mechanism to detect 

a record being locked without waiting for the record. 


ALGOL Programming Reference Manual Volume 2 

Product Interfaces 

Section 4, Using the Enterprise Database Server Interface 

BDMSALGOL Statements 

BDMS LOCK Statement 

Add a new NOWAIT option to the syntax diagram 

after the LOCK/MODIFY verb as follows: 

 

---- LOCK------------------------ 

|-- MODIFY--| |-- NOWAIT --| 

Add the following paragraph under 'Explanation', after the 

paragraph that reads 'If the record or structure... 

with a DEADLOCK exception.' 

If the NOWAIT option is specified and the record or structure 

to be locked has already been locked by another program, 

the present program will not wait for the record or structure. 


DMS SECURE NOWAIT Enhancement 

SYMPTOMS: 

A new NOWAIT option has been added to the SECURE 



6 6875 9497–003



ALGOL Programming Reference Manual Volume 2 

Product Interfaces 

Section 4, Using the Enterprise Database Server Interface 

BDMSALGOL Statements 

SECURE Statement 

Add a new NOWAIT option to the syntax diagram 

after the SECURE verb as follows: 

 

---- SECURE--------------------------- 

|-- NOWAIT --| |----| 


paragraph that reads 'If the record or structure... 

with a DEADLOCK exception.' 

If the NOWAIT option is specified and the record or structure 



ASSISTANT 

Component: ASSISTANT PRI-11472061 

RUN and START With Accesscode 

SYMPTOMS: 

If a usercode has the attribute ACCESSCODENEEDED set, the usercode 

cannot be specified with the USING modifier in a START statement 

(the job will fail with a syntax error.) 


You can now use the WITH modifier to associate an 

accesscode with a RUN or START command. A WITH modifier can only 

occur when the USING modifier is used. 

In the Parameter-File Statements section of the System Assistant 

Operations and Programming guide, the RUN statement and START 

statement railroad diagrams now allow the WITH modifier: 

----+----------------------------------------------------+------| 

| | 

+-- USING -- --+-----------------------+--+ 

| | 

+-- WITH --+ 

6875 9497–003 7


Explanation: 

WITH An option that applies an accesscode to the 

program or job execution. 

If an accesscode is specified, Assistant will verify that the 

accesscode is present in the ACCESSCODELIST attribute of the 

usercode. 

A parameter file that contains a WITH modifier can 

only be used by an Assistant that recognizes the modifier. 

Component: ASSISTANT PRI-11472745 


SYMPTOMS: 











----+----------------------------------------------------+------| 

| | 

+-- USING -- --+-----------------------+--+ 

| | 

+-- WITH --+ 

Explanation: 





usercode. 



8 6875 9497–003

Component: ASSISTCOMPILER PRI-11472044 



SYMPTOMS: 











----+----------------------------------------------------+------| 

| | 

+-- USING -- --+-----------------------+--+ 

| | 

+-- WITH --+ 

Explanation: 





usercode. 



Component: PROPERTIES PRI-11472036 


SYMPTOMS: 







6875 9497–003 9






----+----------------------------------------------------+------| 

| | 

+-- USING -- --+-----------------------+--+ 

| | 

+-- WITH --+ 

Explanation: 





usercode. 



Component: TOOLS PRI-11472052 


SYMPTOMS: 











----+----------------------------------------------------+------| 

| | 

+-- USING -- --+-----------------------+--+ 

| | 

+-- WITH --+ 

Explanation: 



10 6875 9497–003




usercode. 



BCMANAGER 

Component: DR PRI-11535879 

Add Support for Local Recovery Hosts 


Changes to the Business Continuity Installation and Operations 

Guide 

Within Section 4 - Using BC Accelerator. 

Subsection titled "Specifying Constellation Settings to 

Assign User-Specified Values for Each Host in the BC 

Constellation" 

The add a row to the table after the description for "Host 

Name" as follows: 

Within the "Field" column insert "Local Recovery Host" 

Within the "Description" column insert the text; 

A Yes values indicates the host is part of a local 

recovery pair. The next host must also have a yes 

value. 

The value for Brocade on the General Settings form must 

also be Yes. 

Local Recovery and High Availability are mutually 

exclusive for the same host. 

6875 9497–003 11



Support Recovery of Several Hosts by One DR Host 



Guide 





The add a row to the table after the description for "Backup 

PK" as follows: 

Within the "Field" column insert "Alternate site" 


This integer value is the host/site number that is 

used to recover this host. This site uses the disk 

(PK) specified to be the standby halt/load unit for 

the alternate site. A constellation of two hosts would 

have a value of 2 in this field. A constellation of 

three hosts where hosts 1 and 2 are both recovered by 

host 3 would have a value of 3. 

This value is not used for High Availability (HR) and 

Local Recovery (LR) sites. However, if hosts 1 and 2 

are HA or LR hosts and host 3 is a remote disaster 

recovery host, this value is 3. 

Subsection titled "Specifying Mirrors Settings for EMC DMX 

and CLARiiON Subsystem" 

Within the table: 

Change the text under the column named "Field" from 

"TCP/IP address of remote storage management PC(s)" 

to "TCP/IP address of storage management appliances" 

Within the "Description" column in the same row was" 

"Specifies the TCP/IP addresses of the primary and 

secondary remote storage management computers." 

To the following: 

"Specifies the TCP/IP addresses of the storage management 

appliance located at each host site. Specify 

one address for each of the host names (sites) provided 

12 6875 9497–003


earlier. Each TCP/IP address is for the storage 

management appliance local to the host name of the same 

number. 

It is important that the TCP/IP address correspond to the 

location where that host name is located because this 

becomes the preferred appliance to use when moving a host 

to that location. 

For example when host 1 is being moved to host/site 4, the 

storage management appliance at site 4 should be used." 


Add Support for Local Recovery Hosts 



Guide 





The add a row to the table after the description for "Host 

Name" as follows: 

Within the "Field" column insert "Local Recovery Host" 


A Yes values indicates the host is part of a local 

recovery pair. The next host must also have a yes 

value. 

The value for Brocade on the General Settings form must 

also be Yes. 

Local Recovery and High Availability are mutually 

exclusive for the same host. 

6875 9497–003 13



Support Recovery of Several Hosts by One DR Host 



Guide 





The add a row to the table after the description for "Backup 

PK" as follows: 

Within the "Field" column insert "Alternate site" 


This integer value is the host/site number that is 

used to recover this host. This site uses the disk 

(PK) specified to be the standby halt/load unit for 

the alternate site. A constellation of two hosts would 

have a value of 2 in this field. A constellation of 

three hosts where hosts 1 and 2 are both recovered by 

host 3 would have a value of 3. 

This value is not used for High Availability (HR) and 

Local Recovery (LR) sites. However, if hosts 1 and 2 

are HA or LR hosts and host 3 is a remote disaster 

recovery host, this value is 3. 

Subsection titled "Specifying Mirrors Settings for EMC DMX 

and CLARiiON Subsystem" 

Within the table: 

Change the text under the column named "Field" from 

"TCP/IP address of remote storage management PC(s)" 

to "TCP/IP address of storage management appliances" 

Within the "Description" column in the same row was" 

"Specifies the TCP/IP addresses of the primary and 

secondary remote storage management computers." 

To the following: 

"Specifies the TCP/IP addresses of the storage management 

appliance located at each host site. Specify 

one address for each of the host names (sites) provided 

14 6875 9497–003

C 


earlier. Each TCP/IP address is for the storage 

management appliance local to the host name of the same 

number. 

It is important that the TCP/IP address correspond to the 

location where that host name is located because this 

becomes the preferred appliance to use when moving a host 

to that location. 

For example when host 1 is being moved to host/site 4, the 

storage management appliance at site 4 should be used." 

Component: C PRI-11448780 

Default Promotions Apply to Variable Length Argument Lists 

SYMPTOMS: 

Default promotions apply to functions with variable length argument 

lists. 

Functions with variable length argument lists have an argument list 

that ends with a comma followed by an ellipsis. 


In the C Programming Reference Manual, Volume 1: Basic 

Implementation (8600 2268-204); Section 7. Functions; Function 

Syntax; Function Prototype Format, in the description of a variable 

length argument list, add the following before the last sentence in 

the paragraph that begins "At least one argument must be specified 

in the function prototype": 

For undeclared arguments, the compiler makes some adjustments in 

the type of function arguments according to the default argument 

promotions. These adjustments occur on the actual arguments when 

the function is called. These adjustments to the type of the 

actual arguments are the same as described above for functions 

using the old style format. 

6875 9497–003 15


CANDE 

Component: CANDE PRI-11475795 

Implement LI ODT Command 

SYMPTOMS: 

It is difficult to determine the libraries that a task is linked 

to. 


The LI ODT command reports information about libraries that a 

task is linked to. 

In the System Commands Manual (3826 5419-000) add this description 

for the LI command : 

LI (Library Information) 

The LI (Library Information) command reports information about 

libraries that the specified tasks are linked to. 

Syntax 

----LI------------------ 

Explanation 

The report displays the library type, job number, mix number 

and task name of the libraries to which the tasks in the 

are linked. "CL" denotes a connection 

library and "SL" denotes a server library. 

Example 

2188 LI 

3 libraries for mix 2188 

Type Job Task 

SL 341/ 341 *SYSTEM/GENERALSUPPORT 

CL 463/ 463 *SYSTEM/BNA/SUPPORT/53143 


Note: There may be multiple linkages shown to a connection 

library. 

In the CANDE Operations Manual (8600 1500-505) add this description 

for the LI control command : 

?LI 

16 6875 9497–003

Syntax 

--?--------------------LI------------------ 

| | 

|--| 

Explanation 


The ?LI command reports information about libraries to which 

the specified task is linked. If a is not 

specified, the command reports information on the program 

currently running. 


and task name of the libraries to which the task is linked. 

"CL" denotes a connection library and "SL" denotes a server 

library. 

Example 

?LI 


Type Job Task 





library. 

In Section 7 (Getstatus Type 6) of the GETSTATUS/SETSTATUS manual 

(8600 0346-412) add this description for SUBTYPE 18 calls : 

SUBTYPE 18 Calls (Library Information) 

For SUBTYPE 18, GETSTATUS reports library information for a list 

of mix numbers. 

Input 

The caller should set up the array ARY as follows: 

Word Field Description 

ARY [0] [19:20] index to the result area. The area between 

ARY [1] and the result area contains mix 

number request groups. This area must contain 

an even number of words; otherwise, hard 

error 34 is returned. 

ARY [1] through Mix number request groups. 

ARY [ARY [0]-1] 

6875 9497–003 17


The format of a mix number request group is as follows: 

Word Field Name Field Description 

ARY [n] 0 

ARY [n+1] GS_TASKNO_F [39:40] Mix number of the process to 

report 

The SUBCLASS parameter determines how an out-of-space condition 

is handled. Set bit 37 of the SUBCLASS parameter if you want 

GETSTATUS 

to return partial library information when the array parameter 

is not large enough to contain all the requested information for 

a mix number. 

Results Returned 


ARY [n] GSERRORF [47:01] 1 = There was an error obtaining 

data for the specified mix number. 

GSADDLINFOF [46:08] If ARY[n].[47:01] = 1 then this 

field contains the error value 

associated with trying to obtain the 


GS_INDEX_F [19:20] The word index to where the 

information for this mix starts. 

ARY [n+1] GS_TASKNO_F [39:40] Mix number of the process. 

GETSTATUS replaces ARY [n].[19:20] of each mix number entry with 

a link pointing to a structure containing links to library 

information for that mix number. The link value is 0 if no 

libraries are found for that mix number. 

If GETSTATUS finds linked libraries for a given mix number, the 

value in ARY [n].[19:20] is the index of the word in the ARY 

array parameter of the library link structure for that mix 

number. The first word in the library link structure is the 

number of linked libraries. For each library there is a link word 

pointing to a library information structure. 

The library information structure is 2 to 4 words long, depending 

on the bits in the MASK parameter. The first word (word 0) is a 

validity mask. (See Table 7-nn for details of the items addressed 

by each MASK bit.) If a validity mask bit is on, then the 

corresponding library information structure word is valid. 

(See Figure 7-nn for details.) All of the values are returned 

as single words, except the task name, which is a word offset 

from the library link structure into the array of the task's 

name in standard form. 

18 6875 9497–003


If an error occurs, such as an invalid mix number, then the soft 

error result is returned as follows. ARY [n].[47:01] of the mix 

number entry is set to 1. ARY [n].46:08] of the mix number entry 

contains the number of the soft error. 

If there is not enough room in the array for all the information 

requested, GETSTATUS sets bit [47:01] of word 0 of the array 

parameter to 1. If an out-of-space condition occurs while adding 

specific file information and bit 37 of the SUBCLASS parameter is 

set to 1, the mask word in the file information structure for all 

subsequent files is 0. If bit 37 of the SUBCLASS parameter is set 

to 0, and the out-of-space condition occurs, no information is 

returned for mix number. You should make another call with a 

larger array or with fewer mix numbers. If the array is already 

of maximum size, and the out-of-space condition occurs for the 

first mix number, you should make another call with bit 37 of the 

SUBCLASS parameter set to 1. 

Mix number structure 

|count of mix|link/mix |......|link/mix |link/mix | 

|numbers *2 |number group|......|number group|number group| 

| |number 1 |......|number n-1 |number n | 

Library link structure 

|count of |library|.........|library|library| 

|libraries|link |.........|link |link | 

Library information structure 

X X+1 X+2 X+3 

|Validity|Task |Job |Mix | 

|mask |name |number|number| 

Figure 7-nn Mix Number Links 

Table 7-nn Corresponding Library Information For Each Mix Number 

Mask bit Name Description 

0 TASKNAME Link to the library name 

1 JOBNUMBER Job number of the library 

2 MIXNUMBER Mix number of the library 


Count Incorrect Accesspassword Against SECOPT 

LOGONATTEMPTS 

SYMPTOMS: 

Repeatedly entering an invalid accesspassword when one is required 

at log-on time incurs no penalty. 

6875 9497–003 19



Entering an incorrect accesspassword when one is required at 

log-on time now counts as a failed log-on attempt against the 

limit established by the system security option LOGONATTEMPTS. 


COMPILE AS $ Replaces Source File 

SYMPTOMS: 

When AS $ is specified in a COMPILE or BIND 

command, and a source file named exists, 

that file is replaced by the new code file. 



command, and file named exists, that file 

is now replaced by the new code file only if its FILEKIND value 

falls between those of COMPILERCODEFILE (20) and CODEFILE (63), 

inclusive. Those FILEKIND values denote codefiles. The intention 

is to prevent the replacement of a source file or other noncodefile 

while still allowing replacement of an existing codefile. 


Add ARCHIVE, CATALOG, MODIFY, And MKDIR Verbs 


CANDE now allows the WFL statements ARCHIVE, CATALOG, MODIFY, 

and MKDIR to be used as CANDE verbs, without having to prefix them 

with "WFL". 


Add ARCHIVE, CATALOG, MODIFY, And MKDIR Verbs 


CANDE now allows the WFL statements ARCHIVE, CATALOG, MODIFY, 

and MKDIR to be used as CANDE verbs, without having to prefix them 

with "WFL". 

20 6875 9497–003


COMPILE AS $ Replaces Source File 


SYMPTOMS: 


command, and a source file named exists, 

that file is replaced by the new code file. 



command, and file named exists, that file 

is now replaced by the new code file only if its FILEKIND value 

falls between those of COMPILERCODEFILE (20) and CODEFILE (63), 

inclusive. Those FILEKIND values denote codefiles. The intention 

is to prevent the replacement of a source file or other noncodefile 

while still allowing replacement of an existing codefile. 


Explain "CANDE SERVICE UNAVAILABLE" Message 

SYMPTOMS: 

The message 

#CANDE SERVICE UNAVAILABLE; MAX STATIONS EXCEEDED 

is not documented. 


Please add the following sentence at the end of the explanation of 

the ?MAXSTATIONS Network Control Command in the CANDE Configuration 

Reference Manual, form number 8600 1344: 

When the maximum number of stations has been reached, and 

an attempt is made to initialize another station, CANDE 

produces the message 


6875 9497–003 21



Explain "CANDE SERVICE UNAVAILABLE" Message 

SYMPTOMS: 

The message 


is not documented. 


Please add the following sentence at the end of the explanation of 

the ?MAXSTATIONS Network Control Command in the CANDE Configuration 

Reference Manual, form number 8600 1344: 

When the maximum number of stations has been reached, and 

an attempt is made to initialize another station, CANDE 

produces the message 


CENTRALSUPP 

Component: CCSFILE PRI-11494871 

Changes To Mappings Involving EBCDICUTL 

SYMPTOMS: 

On certain terminals and printers used in Taiwan, the EBCDICUTL 

Start Double Octet (SDO, x2B) and End Double Octet (EDO, x2C) 

characters consume a visual space. When EBCDICUTL characters are 

mapped to UCS2 or UCS2NT characters, no space is inserted on the 

transitions between 8-bit and 16-bit characters in the source, 

causing an unexpected visual representation. 


Coded character set mapping between the EBCDICUTL coded character 

set and other coded character sets has been changed. Specifically, 

- The mapping from EBCDICUTL to UCS2 and UCS2NT now inserts 

a space character (x0020 for UCS2, x2000 for UCS2NT) in the 

destination when a transition between 8-bit and 16-bit 

characters occurs in the source. 

- Mapping from UCS2 or UCS2NT to EBCDICUTL is no longer supported. 

- Mapping between EBCDICUTL and CODEPAGE950 or WINBIG5, in either 

direction, is no longer supported. 

22 6875 9497–003


In tabular form, the mappings for the following combinations 

involving EBCDICUTL were previously supported: 

Source Destination Source Destination 

Coded Character Coded Character INTMODE INTMODE 

Set Name Set Name and EXTMODE and EXTMODE 

Integer Integer 

Value Value 

CODEPAGE950 EBCDICUTL 110 108 

EBCDICUTL CODEPAGE950 108 110 

EBCDICUTL UCS2 108 85 

EBCDICUTL UCS2NT 108 84 

EBCDICUTL WINBIG5 108 115 

UCS2 EBCDICUTL 85 108 

UCS2NT EBCDICUTL 84 108 

WINBIG5 EBCDICUTL 115 108 

With this change, only these mappings of combinations 

involving EBCDICUTL are now supported: 





Value Value 



Component: CCSFILE PRI-11539483 


SYMPTOMS: 














6875 9497–003 23











Value Value 















Value Value 



Component: CENTRALSUPPORT PRI-11525687 


SYMPTOMS: 








24 6875 9497–003

















Value Value 















Value Value 



Component: CENTRALSUPPORT PRI-11539475 


SYMPTOMS: 




6875 9497–003 25





















Value Value 















Value Value 



26 6875 9497–003

CLEARPATHEPORTAL 

Component: MCP PRI-11437923 

ePortal Software Installation During Cold Start 


SYMPTOMS: 

ePortal Software Installation Warning Messages During Cold Start. 


Make the following changes to the ClearPath Plus Servers 

ClearPath ePortal Implementation and Operations Guide(6891 8986- 

004): 

Add the following section between 6.2.2. Installing the ClearPath 

ePortal Interim Correction and 6.2.3. Installing and Verifying 

ClearPath ePortal Image Files 

Installing ClearPath ePortal Software During Cold Start of MCP System 

If ClearPath ePortal software is installed while the MCP system 

is cold-started, the ClearPath ePortal installation assumes the 

default family of the APPLIANCES share to be the Simple Install's 

software installation family and ePortal software installation 

continues after displaying the following messages several times: 

ePortal: Waiting for ADMINCENTER, link result = -6,library state = 1 

Make the following changes to the ClearPath ePortal Business 

Implementation and Operations Guide (8215 9641-0000) 

In Section 3 Installing and Configuring MCP Software, 

Add the following section after the Installing the ClearPath ePortal 

Interim Correction(IC) section: 

Installing ClearPath ePortal Software During Cold Start of MCP 

System 

If ClearPath ePortal software is installed while the MCP system 

is cold-started, the ClearPath ePortal installation assumes the 

default family of the APPLIANCES share to be the Simple Install's 

software installation family and ePortal software installation 

continues after displaying the following messages several times: 

ePortal: Waiting for ADMINCENTER, link result = -6,library state = 1 

6875 9497–003 27


COBOL74 

Component: COBOL74 PRI-11452272 

Condition-Name With THRU Not Syntaxed When Not Ascending 

SYMPTOMS: 

When a level 88 condition name is defined with the THROUGH 

phrase, that is 'lit1 THROUGH lit2', then lit1 must be less 

than lit2. The compiler does not flag the condition name 

when this rule is violated. 


COBOL ANSI-74 Programming Reference Manual Volume 1, 

8600 0296-205 requires the following changes. 

Section 7. Data Division 

Data-Description Entry for Condition-Names 

Explanation of Format 3 

Add the following after the paragraph that reads 

"Wherever the THROUGH...less than literal-4, and so forth." 

Note: 

The ascending relation of the literal-1 and literal-2 will 

not be verified by the compiler. If literal-2 is less than 

literal-1, the evaluation of the condition returns FALSE. 

Add the following example as example 7-10. 

Example 7-10 shows the coding of condition-names 

that violates ascending relation of literal-1 less than 

literal-2. 

01 COND-GROUP PIC S9(11) BINARY. 

88 GROUP1 VALUE 1 THRU 10. 


88 GROUP3 VALUE -62 THRU -68. 


MOVE 8 TO COND-GROUP. 

IF GROUP1 DISPLAY "GROUP1". 




IF GROUP2 DISPLAY "IT'S GROUP2!". 

MOVE -66 TO COND-GROUP. 





28 6875 9497–003



At runtime, this program will display the following output. 

DISPLAY:GROUP1. 



ERROR 357 Is Misleading 

SYMPTOMS: 

The size of a record description is the sum of the 

maximum sizes of all items subordinate to a 01-level item. 

The maximum size of a record description is restricted by 

the explicit or implicit usage of the 01-level item. 

When the usage of the 01-level items is REAL, the compiler 

allows a maximum size of 65,535 words. 

When this limit is exceeded however, the compiler issues 

the following misleading message. 

01 WS-USERCODE-TABLE USAGE REAL. 

03 WS-USERCODE-TABLE-REC 

OCCURS 33000. 

05 WS-USERCODE-TOT-RT REAL. 

05 WS-USERCODE-IN-MSGS REAL. 

ERROR 357 : THE MAXIMUM LENGTH OF THE DATA ITEM MUST NOT EXCEED 

65,535 BYTES. *** WS-USERCODE-TABLE 


In the COBOL ANSI-74 Programming Reference Manual 

Volume 1: Basic Implementation (8600 0296-205), 

Section 6 Data Concepts, Records, 

Table 6-1. Usage and Maximum Size of a Record Description, 

Modify the list of usages for 65,535 words from 

TASK, EVENT, INDEX, or LOCK 

to 

TASK, EVENT, INDEX, LOCK, or REAL 


ERROR 357 Is Misleading 

SYMPTOMS: 

The size of a record description is the sum of the 

maximum sizes of all items subordinate to a 01-level item. 

6875 9497–003 29


The maximum size of a record description is restricted by 

the explicit or implicit usage of the 01-level item. 

When the usage of the 01-level items is REAL, the compiler 

allows a maximum size of 65,535 words. 

When this limit is exceeded however, the compiler issues 

the following misleading message. 

01 WS-USERCODE-TABLE USAGE REAL. 

03 WS-USERCODE-TABLE-REC 

OCCURS 33000. 

05 WS-USERCODE-TOT-RT REAL. 

05 WS-USERCODE-IN-MSGS REAL. 

ERROR 357 : THE MAXIMUM LENGTH OF THE DATA ITEM MUST NOT EXCEED 

65,535 BYTES. *** WS-USERCODE-TABLE 




Section 6 Data Concepts, Records, 

Table 6-1. Usage and Maximum Size of a Record Description, 

Modify the list of usages for 65,535 words from 

TASK, EVENT, INDEX, or LOCK 

to 

TASK, EVENT, INDEX, LOCK, or REAL 

COBOL85 


Condition-Name With THRU Not Syntaxed When Not Ascending 

SYMPTOMS: 

When a level 88 condition name is defined with the THROUGH 

phrase, that is 'lit1 THROUGH lit2', then lit1 must be less 

than lit2. The compiler does not flag the condition name 

when this rule is violated. 




Section 4. Data Division 

Data Description Entry Format 3: Level-88 Condition-Name Entry 

Under 'literal-1 THROUGH literal-2' heading, add the following 

after the existing paragraph. 

Note: 

The ascending relation of the literal-1 and literal-2 will 

30 6875 9497–003


not be verified by the compiler. If literal-2 is less than 

literal-1, the evaluation of the condition returns FALSE. 

Example 

Following example shows the coding of condition-names 

that violates ascending relation of 'literal-1 less than 

literal-2'. 

01 COND-GROUP PIC S9(11) BINARY. 

















At runtime, this program will display the following output. 




Only Last $LI_SUFFIX Is Applied 

SYMPTOMS: 

When only one LI_SUFFIX compiler option is used, it is used for all 

statements in the program. If more than one LI_SUFFIX option is 

used 

in the same program, then the last LI_SUFFIX is used for all of the 

statements in the program. 

The manual is not clear that the last LI_SUFFIX is going to be used 

in the entire program. 


Please add the following sentences to COBOL ANSI-85 Programming 

Reference Manual, Volume 1: Basic Implementation (8600 1518-308) 

in section 15 - Compiler Operations, under Compiler Options 

(page 15-68). 

6875 9497–003 31


"The value of LI_SUFFIX at the end of the program is used for all 

statements in the program. If a nested program is used, then the 

value of LI_SUFFIX at the end of the nested program is used for all 

statements in the nested program." 


Unlimited Nesting Of $INCLUDE Can Loop Forever 

SYMPTOMS: 

The COBOL85 compiler terminates with a fault if a recursive 

$INCLUDE CCR is encountered. 


Add the following text in the COBOL ANSI-85 Programming Reference 

Manual Volume 1: Basic Implementation (8600 1518-309) under 

the Section 15 - Compiler Operations, Compiler Options, INCLUDE 

option, page 15-57, after the second paragraph of 'file title'. 

The INCLUDE options specified in circular manner will result in 

internal compiler error. 



SYMPTOMS: 






8600 1526-204, 

Section 3. Using the Enterprise Database Server Program Interface, 

Manipulating Data in a Database, 

LOCK/MODIFY Statement, 

Add a new NO WAIT option to the syntax diagram 


{LOCK } [ NO WAIT ] ... 

{---- } [ -- ---- ] 

{MODIFY } 

{----- } 

32 6875 9497–003



paragraph that reads 'You cannot free structure... 

earlier is this section.' 

If the NO WAIT option is specified and the record or structure 





SYMPTOMS: 






8600 1526-204, 







{---- } [ -- ---- ] 

{MODIFY } 

{----- } 








Procedure Division Header (Change) Documentation Is Incorrect 

SYMPTOMS: 

The chapter 'Changes That Probably Affect Your Programs' of the 

COBOL ANSI-85 Programming Reference Manual Volume 1: Basic 

Implementation (8600 1518-309) in the page F-22 states that 

6875 9497–003 33


'A data item appearing in the USING phrase of the Procedure 

Division header must not have a REDEFINES clause in its data 

description entry'. This restriction already exists for ASERIES 

COBOL74 and users migrating from A Series COBOL74 will not be 

affected. 


Please delete the following text from the COBOL ANSI-85 Programming 

Reference Manual Volume 1: Basic Implementation (8600 1518-309) 

under the Appendix F - Comparison of COBOL Versions, Changes That 

Probably Affect Your Programs, Procedure Division Header (Change), 

in page F-22. The same is mentioned below: 

Procedure Division Header (Change): 

A data item appearing in the USING phrase of the Procedure Division 

header must not have a REDEFINES clause in its data description 

entry. 

Allowing an item with a REDEFINES clause to be specified in the 

USING phrase of the Procedure Division header could allow 

programming errors to remain undetected. 

If your program specified a redefined item in the USING phrase of 

the Procedure Division header, you can convert it by substituting 

the redefined item, as in the following syntax: 

. 

. 

. 

01 DUMMY. 

03 A PIC 9(10). 

03 B REDEFINES A PIC X(10) 

. 

. 

. 

PROCEDURE DIVISION USING A. 


Migration Issue with COBOL85 COMMON Clause 

SYMPTOMS: 

In COBOL85, data items declared with a COMMON clause in a program 

compiled at lexicographic level 3 or higher are matched by 

name and type to the global directory of the host. When the 

program is bound to the host, the COMMON data items are placed 

at the lexicographic level of the host program. 

The COBOL Migration section of the COBOL85 Program Reference 

Manual states that all references to GLOBAL must be changed 

to COMMON for COBOL85, but the above information is missing. 

34 6875 9497–003

It should be documented in the COBOL ANSI-85 

Programming Reference Manual, Volume 1. 





Appendix G. COBOL Migration, 

Changes That Probably Affect Your Programs, 

GLOBAL Clause (Change), 

add the following text at the end of the current paragraph. 

In COBOL85, data items declared with a COMMON clause in a program 

compiled at lexicographic level 3 or higher are matched by 

name and type to the global directory of the host. When the 

program is bound to the host, the COMMON data items are placed 

at the lexicographic level of the host program. 


Migrating From COBOL68 Where This Program Compiles Okay With 

COBOL74 

SYMPTOMS: 

This program compiles okay with COBOL74 but results in syntax 

errors with COBOL85. 

$ SET WARNFATAL ERRORLIMIT=999 FEDLEVEL = 5 

IDENTIFICATION DIVISION. 

ENVIRONMENT DIVISION. 

DATA DIVISION. 

WORKING-STORAGE SECTION. 

77 OP REAL. 

77 ONE BINARY PIC S9(11) VALUE 1. 

77 BIG DOUBLE VALUE 12345678901234567890999. 

77 BIG2 REAL VALUE 12345678901234567890999. 

01 EBIG2 REAL VALUE 12345678901234567890999. 

01 WSREC. 

02 RBIG DOUBLE VALUE 12345678901234567890999. 

02 RBIG2 REAL VALUE 12345678901234567890999. 

01 TYME PIC X(30) TYPE LONG-DATE. 

PROCEDURE DIVISION. 

STRT. 

MOVE ATTRIBUTE OPTION OF MYSELF TO OP 

MOVE ONE TO OP[0:VALUE FAULT:1] 

CHANGE ATTRIBUTE OPTION OF MYSELF TO OP. 

ACCEPT TYME FROM DATE. 

STOP RUN. 

The above program is giving the following syntax error. 

6875 9497–003 35


C W COBOL85 ON SLICE 

#COMPILING 9741 

00110077 BIG2 REAL VALUE 12345678901234567890999. 

1 

1) ERROR: 423 : LITERAL SIZE EXCEEDS DECLARED SIZE 

00120001 EBIG2 REAL VALUE 12345678901234567890999. 

1 


001500 02 RBIG2 REAL VALUE 12345678901234567890999. 

1 


#SNTX 

#ET=0.6 PT=0.1 IO=0.3 


Add the following text in the COBOL ANSI-85 Programming Reference 

Manual Volume 1: Basic Implementation (8600 1518-309) under the 

Appendix F - Comparison of COBOL Versions, Changes That Probably 

Affect Your Programs, in page F-30 just before VALUE OF Clause 

(Obsolete). 

VALUE Clause(Change) : 

In COBOL74, the maximum number of digits that can be specified in a 

numeric literal is 23 digits for REAL. 

In COBOL85, the maximum number of digits that can be specified in a 

numeric literal is 12 digits for REAL. 


$INCLUDEd Lines In A COPY Get LISTed Unconditionally 

SYMPTOMS: 

The $LISTINCL option is false but the lines included by the COPY 

statement appear in the listing. The LISTINCL option has no effect 

on source language records included with the COPY statement in the 

compilation listing of the program. This fact needs to be 

documented. 

Consider the example below: 

001000$SET LIST 

002000 IDENTIFICATION DIVISION. 

003000 ENVIRONMENT DIVISION. 

004000 DATA DIVISION. 

005000 WORKING-STORAGE SECTION. 

006000 COPY CARD FROM 10000 TO 10000. 

007000 PROCEDURE DIVISION. 

008000 P. DISPLAY SOMETHING STOP RUN. 

009000$SET OMIT 

0010000$INCLUDE CARD ("TEXT") 

36 6875 9497–003

0011000$ COPYBEGIN "TEXT" 

0012000 77 SOMETHING PIC X(9) VALUE "SOMETHING". 

0013000$COPYEND "TEXT" 

The output listing contains list of $include 

006000 COPY CARD FROM 10000 TO 10000. 

2:012000 77 SOMETHING PIC X(9) VALUE "SOMETHING". 

007000 PROCEDURE DIVISION. 




Volume 1: Basic Implementation (8600 1518-309), Section 15. 

Compiler Operations, Compiler Options, LISTINCL Option, update the 

following text after the last sentence. 

The LISTINCL option does not affect the COPY statement. 



SYMPTOMS: 






8600 1526-204, 



SECURE Statement, 



SECURE [ NO WAIT ] ... 

------ [ -- ---- ] 


paragraph that reads 'If you use the STRUCTURE option... 

are securing the structure.' 




6875 9497–003 37




SYMPTOMS: 






8600 1526-204, 







------ [ -- ---- ] 








Array Parameter Passed To COMS Service Function 

SYMPTOMS: 

When a program calls a service function from the Transaction 

Server Program Interface, an array parameter passed to a 

function must be declared at 77 or 01 level. 

This rule should be documented in the COBOL ANSI-85 

Programming Reference Manual, Volume 2. 



Volume 2: Product Interfaces (8600 1526-204) 

Section 2 Using the Transaction Server Program Interface 

Using Service Functions 

Passing Parameters to Service Functions 

38 6875 9497–003

After the paragraph that states "The service function 

declarations and valid parameters.. following general 

characteristics:", add the following sentence in the 

third bullet item that states "An array is an EBCDIC 

or integer array." 

An array must be declared at 77 or 01 level. 


Document OCCURS Maximum Limit 

SYMPTOMS: 

The OCCURS limit depends on the USAGE of the data item 

and the 01 level record size. This fact needs to be 

documented. 




Section 4. Data Division, 

Data Description Entry Format 1, 

OCCURS Clause, 

integer 2, 

add the following paragraph at the end of the current 

paragraph. 


The limit of the maximum number of occurrences depends 

on the USAGE of the entity and the maximum record size. 


Document OCCURS Maximum Limit 

SYMPTOMS: 

The OCCURS limit depends on the USAGE of the data item 

and the 01 level record size. This fact needs to be 

documented. 




Section 4. Data Division, 

Data Description Entry Format 1, 

OCCURS Clause, 

integer 2, 

6875 9497–003 39



paragraph. 

The limit of the maximum number of occurrences depends 

on the USAGE of the entity and the maximum record size. 


Document Bindinfo Difference Between COBOL74 And COBOL85 

SYMPTOMS: 

COBOL85 emits different BINDINFO than COBOL74 for file 

records and 77 level data items specified with the OWN clause. 

In COBOL74, the name of the file is appended to the name of 

the record. 

In COBOL85, the record name remains the same. 

In COBOL74, the name of a 77 level item with the OWN clause 

has '/77' appended to the name. 


remains the same. 

These differences needs to be documented. 




Appendix F. Comparison of COBOL Versions 

Changes That Probably Affect Your Programs 

Binding, 


paragraph. 




the record. 






40 6875 9497–003



Document Bindinfo Difference Between COBOL74 And COBOL85 

SYMPTOMS: 




the record. 






These differences needs to be documented. 




Appendix F. Comparison of COBOL Versions 

Changes That Probably Affect Your Programs 

Binding, 


paragraph. 




the record. 







File Status "04" Is Not Implemented 

SYMPTOMS: 

Reading a variable length record sequential file gives the file 

status 00 instead of 04. Programs for writing and reading a 

variable length record sequential file are given below- 

6875 9497–003 41


COBOL85 Write Program- 



INPUT-OUTPUT SECTION. 

FILE-CONTROL. 

SELECT SECFILE ASSIGN TO DISK 

ORGANIZATION IS SEQUENTIAL 

ACCESS IS SEQUENTIAL. 


FILE SECTION. 

FD SECFILE 

BLOCK CONTAINS 1200 CHARACTERS 

RECORD IS VARYING IN SIZE FROM 1 TO 30 CHARACTERS 

DEPENDING ON REC-SIZE. 

01 SECREC. 

03 REC PIC X(30). 


77 REC-SIZE PIC 9(4). 


P-0. 

OPEN OUTPUT SECFILE. 

PERFORM P-1 12 TIMES. 

CLOSE SECFILE LOCK. 

STOP RUN. 

P-1. 

MOVE "ABCDEF" TO REC. 

MOVE 6 TO REC-SIZE. 

WRITE SECREC. 

MOVE "ABCDEF ABCDEFGHIJ" TO REC. 


WRITE SECREC. 

Compile and run the above program. It will create a variable length 

record file "SECFILE". 

COBOL85 Read Program- 

$SET FS4XCONTINUE 




FILE-CONTROL. 



ACCESS IS SEQUENTIAL 

FILE STATUS IS FS-1. 


FILE SECTION. 

FD SECFILE 


RECORD CONTAINS 6 TO 10 CHARACTERS. 

01 SECREC. 

03 REC PIC X(10). 


77 FS-1 PIC X99. 

42 6875 9497–003


P-0. 

OPEN INPUT SECFILE. 

DISPLAY FS-1. 


CLOSE SECFILE. 

STOP RUN. 

P-1. 

READ SECFILE. 

DISPLAY FS-1. 

DISPLAY SECREC. 


Compile and run the above program. It will give the following result- 

C 


#ET=0.1 PT=0.1 IO=0.0 

R 

#RUNNING 8620 

#8620 WARNING 47: LOGICAL FILE MAXRECSIZE INCONSISTENT WITH PERMANENT 

FILE MAXRECSIZE @ (21000) 

#8620 WARNING 51: LOGICAL FILE MINRECSIZE INCONSISTENT WITH PERMANENT 

FILE MINRECSIZE @ (21000) 

#8620 DISPLAY:00. 

#8620 DISPLAY:00. 

#8620 DISPLAY:ABCDEF. 

#8620 DISPLAY:00. 

#8620 DISPLAY:ABCDEF ABC. 

#8620 DISPLAY:00. 


#8620 DISPLAY:00. 


#8620 DISPLAY:00. 


#ET=0.2 PT=0.0 IO=0.1 


Remove the second row of the table 3.1 for I-O status 04 in the COBOL 

ANSI-85 Programming Reference Manual Volume 1: Basic Implementation 

(8600 1518-309) under the Section 3 - Environment Division, 

Input-Output Section, I-O Status Code, Table 3-1. I-O Status Codes: 

Successful Execution at page 3-50. 

SRI 04 A READ statement was successfully executed, but 

the length of the record that was processed did not 

conform to the fixed file attributes for that file. 

6875 9497–003 43



File Status "04" Is Not Implemented 

SYMPTOMS: 

Reading a variable length record sequential file gives the file 

status 00 instead of 04. Programs for writing and reading a 

variable length record sequential file are given below- 

COBOL85 Write Program- 




FILE-CONTROL. 



ACCESS IS SEQUENTIAL. 


FILE SECTION. 

FD SECFILE 


RECORD IS VARYING IN SIZE FROM 1 TO 30 CHARACTERS 

DEPENDING ON REC-SIZE. 

01 SECREC. 

03 REC PIC X(30). 


77 REC-SIZE PIC 9(4). 


P-0. 

OPEN OUTPUT SECFILE. 


CLOSE SECFILE LOCK. 

STOP RUN. 

P-1. 

MOVE "ABCDEF" TO REC. 


WRITE SECREC. 

MOVE "ABCDEF ABCDEFGHIJ" TO REC. 


WRITE SECREC. 

Compile and run the above program. It will create a variable length 

record file "SECFILE". 

COBOL85 Read Program- 

$SET FS4XCONTINUE 




FILE-CONTROL. 



44 6875 9497–003

ACCESS IS SEQUENTIAL 

FILE STATUS IS FS-1. 


FILE SECTION. 

FD SECFILE 


RECORD CONTAINS 6 TO 10 CHARACTERS. 

01 SECREC. 

03 REC PIC X(10). 


77 FS-1 PIC X99. 


P-0. 

OPEN INPUT SECFILE. 

DISPLAY FS-1. 


CLOSE SECFILE. 

STOP RUN. 

P-1. 

READ SECFILE. 

DISPLAY FS-1. 

DISPLAY SECREC. 


Compile and run the above program. It will give the following 

result- 

C 


#ET=0.1 PT=0.1 IO=0.0 

R 

#RUNNING 8620 

#8620 WARNING 47: LOGICAL FILE MAXRECSIZE INCONSISTENT WITH 

PERMANENT FILE MAXRECSIZE @ (21000) 

#8620 WARNING 51: LOGICAL FILE MINRECSIZE INCONSISTENT WITH 

PERMANENT FILE MINRECSIZE @ (21000) 

#8620 DISPLAY:00. 

#8620 DISPLAY:00. 

#8620 DISPLAY:ABCDEF. 

#8620 DISPLAY:00. 


#8620 DISPLAY:00. 


#8620 DISPLAY:00. 


#8620 DISPLAY:00. 


#ET=0.2 PT=0.0 IO=0.1 


Remove the second row of the table 3.1 for I-O status 04 in the 

COBOL ANSI-85 Programming Reference Manual Volume 1: Basic 

Implementation (8600 1518-309) under the Section 3 - Environment 

Division, Input-Output Section, I-O Status Code, Table 3-1. I-O 

Status Codes: 

Successful Execution at page 3-50. 

6875 9497–003 45


COMS 

SRI 04 A READ statement was successfully executed, but 

the length of the record that was processed did not 

conform to the fixed file attributes for that file. 

Component: COMS PRI-11551599 

Delete Unused Stations And Associated Hosts 

SYMPTOMS: 

Unused stations and hosts accumulate in the COMS configuration 

file. There needs to be an automatic way to remove these unused 

stations and hosts so that COMS tables do not reach their limits. 


A new integer attribute has been implemented for the Global Entity 

and is permanently stored in the Configuration File. This 

attribute is called "Delete Stations/Hosts Not Logged-On For n 

Days". Its default value is zero indicating that COMS will not 

automatically delete stations and hosts. 

If this attribute is set to a value greater than zero, COMS will 

delete any stations that have not logged on to COMS in days. 

In addition, if the host associated with the station that is being 

deleted is not being used by any other station, it is also deleted. 

This new attribute can be examined and modified by both the COMS 

Utility Program and a COMS program agent. Changes to this 

attribute are preserved when COMS is brought down and back up. 

System log messages are issued indicating how many stations and 

hosts were deleted. 

The following information needs to be added to the Transaction 

Server Configuration Guide, form number 8600 0312: 

In Section 4, in Using the COMS Utility Program, under Defining 

Transaction Server Global Attributes, add the following: 

To the bulleted list at the beginning of the section add: 

. Delete unused stations and hosts 

To the figure 'Figure 4-8. The Global Activity Menu', add 

the following line immediately after the line starting with 

'View Buffers Cached': 

Delete Stations/Hosts Not Logged-On For [0 ] Days 

To the table containing Field Name and Explanation add the 

following to the end of the table: 

46 6875 9497–003


Field Name - Delete Stations/Hosts Not Logged-On For n Days 

Explanation - Enter an integer value from 0 to 2000. The 

default value is zero. If this value is zero, COMS will 

not delete unused stations or hosts. If this value is 

greater than zero, COMS will delete any stations that have 

not logged on to COMS in days and any stations that 

have never logged on. In addition, if the host associated 

with the station that is being deleted is not being used 

by any other station, it is also deleted. A diagnostic 

log message and a DISPLAY will be issued whenever COMS 

deletes any stations. The message will indicate whether 

the cleanup process has completed or is still ongoing. 

To the railroad diagram at the end of the section add: 

DELETE_STATION_DAYS --- = 

DSD -----------------| 


Server Programming Guide, form number 8600 0650: 

In Section 10, in Configuration Message Formats, under Global 

Entity, add the following to the existing railroad diagram: 


DSD -----------------| 

In Section 10, in Attribute Field ID Numbers and Data Types, under 

Table 10-15 - Global Datarecord Attribute Values, add the following 

entry to the end of the table: 

Global Attribute Field ID Data Type 

DELETE_STATION_DAYS 11 Integer 



SYMPTOMS: 










6875 9497–003 47





































DSD -----------------| 






DSD -----------------| 

48 6875 9497–003








Disabling Programs When Program Fails To Initiate 

SYMPTOMS: 

When a program fails to initiate, COMS disables the program with 

the NOW option. There needs to be an automatic way to choose 

whether such a program is disabled with or without the NOW option. 


A new boolean attribute has been implemented for the Global Entity 


attribute is called "Disable NOW Program On Init Failure". It 

determines how COMS disables programs that fail to initiate. The 

two possible ways that COMS can disable such a program is with or 

without the NOW option. 

The default value is NO, indicating that COMS disables any program 

that fails to initiate without the NOW option. For versions of 

COMS without this feature, programs that failed to initiate were 

disabled with the NOW option and there was no option to change this 

behavior. 

The NOW option causes a program to be disabled immediately. Any 

subsequent input is queued and waits for the program to be enabled. 

If the NOW option is not specified, the program is disabled after 

all of its queued input is processed. Any subsequent input is 

rejected and returned to the submitter. 








Change the first paragraph to: 

Twelve global attributes are predefined for the system. The 

first six attributes are concerned with queuing input and 

6875 9497–003 49


tanking output. The remainder of the attributes address 

system-wide Transaction Server options: 

To the end of the bulleted list at the beginning of the 

section add: 

. Disable options for programs that fail to initiate 


the following line immediately after the last line: 

Disable NOW Program On Init Failure . . [N] 



Field Name - Disable NOW Program On Init Failure 

Explanation - Specify whether programs that fail to initiate 

are disabled with or without the NOW option. If you 

enter Y (yes), COMS will disable programs that fail to 

initiate with the NOW option. If you enter N (no), COMS 

will disable programs that fail to initiate without the NOW 

option. The default value is N (no). 


DISABLE_NOW_PROGRAM --- = 

DNP -----------------| 






DNP -----------------| 





DISABLE_NOW_PROGRAM 12 Boolean 



SYMPTOMS: 




50 6875 9497–003













behavior. 



















section add: 














6875 9497–003 51




DNP -----------------| 






DNP -----------------| 






Component: PAF PRI-11555098 

Session Language is Ignored When Using The Update Command 

SYMPTOMS: 

Errors encountered when using the Update command are always displayed 

in English. 


The following error values and messages should be added to 

table 10-66 in Section 10 of the COMS Transaction Server Programming 

Guide (8600 0650). 

------------------------------------------------------------------- 

Value Message 

------------------------------------------------------------------- 

466 Invalid station name format, scanning 

467 Invalid element name format, scanning 

468 Invalid subaddress format, scanning 

469 Attribute expected, scanning 

470 Value out of bounds, scanning 

471 Must be Direct window: 

472 Dump Complete - elements were dumped to 

473 A semantic error occurred, scanning 

------------------------------------------------------------------- 

52 6875 9497–003

Component: PAF PRI-11555101 


Session Language is Ignored When Using The Update Command 

SYMPTOMS: 

Errors encountered when using the Update command are always displayed 

in English. 


The following error values and messages should be added to 

table 10-66 in Section 10 of the COMS Transaction Server Programming 

Guide (8600 0650). 

------------------------------------------------------------------- 

Value Message 

------------------------------------------------------------------- 

466 Invalid station name format, scanning 

467 Invalid element name format, scanning 

468 Invalid subaddress format, scanning 

469 Attribute expected, scanning 

470 Value out of bounds, scanning 

471 Must be Direct window: 

472 Dump Complete - elements were dumped to 

473 A semantic error occurred, scanning 

------------------------------------------------------------------- 

Component: UTILITY PRI-11447988 

Utility Refresh Command Must Be Uppercased And Not 

Abbreviated 

SYMPTOMS: 

The Utility Program allows a screen to be refreshed by transmitting 

REFRESH. No abbreviations or lowercase letters are allowed. This 

command should work like all the other commands in Utility. 


In Section 4 of the Transaction Server for ClearPath MCP 

Configuration Guide, Using the COMS Utility Program, on pages 

4-7 and 4-13 (describing each action and its use), add the 

following text between HOme and SEarch: 

Refresh To display the last output screen, specify Refresh in 

the Action field and transmit. Refresh can be 

abbreviated to one character on all screens except the 

Report Initiation screen, where a minimum of three 

characters is required. Additionally, the Unisys 

Utility Editor shortcut 00 can be used as a 

synonym for refresh. 

6875 9497–003 53




SYMPTOMS: 





































54 6875 9497–003










DSD -----------------| 






DSD -----------------| 








SYMPTOMS: 
















6875 9497–003 55































DSD -----------------| 






DSD -----------------| 






56 6875 9497–003




SYMPTOMS: 















behavior. 



















section add: 


6875 9497–003 57
















DNP -----------------| 






DNP -----------------| 








SYMPTOMS: 











58 6875 9497–003






behavior. 



















section add: 












will disable programs that fail to initiate without the 

NOW option. The default value is N (no). 



DNP -----------------| 


6875 9497–003 59


COMTI 





DNP -----------------| 






Component: COMTI PRI-11583041 

Connector PSH Help Command 


The Connector PSH Help Command has been added to the Help book. 

Component: COMTI PRI-11583059 

Connector PSH Help Command 


The Connector PSH Help Command has been added to the Help book. 

DBCERTIFICATION 

Component: DBCERTIFICATION PRI-11507344 

Invalid Syntax Using CERTIFY ALL With Set Name 

SYMPTOMS: 

Executing the syntax CERTIFY ALL (OPTIONS=SETS()) results 

in an invalid index @ 32060800. 


Please update the Enterprise Database Server for Clearpath MCP 

Utilities Operation Guide Clearpath MCP 12.0 (8600 0759-613), 

60 6875 9497–003

DMSII 


under the Section 11. Checking the Integrity and Performance, under 

Certify Command section under the Restriction section. Please add 

the following after the last the bullet. 

. SETS() is not valid when used in CERTIFY ALL. 

. When is specified, it must correspond to the 

data set specified in the . 

Component: ACR PRI-11428100 

Correctly Handling TranStamp/RSN For Overflow Situation 

SYMPTOMS: 

If the TRANSTAMP went up to 2 ** 46 - 1, an invalid transtamp might 

be used. 

The maximum RSN is incremented from 2 ** 46 - 1 to 2 ** 47 - 1. 


The following change is for the 

The Enterprise Database Server Getting Started and Installation 

Guide (Form number 3850 8198-000). 

Section 12 describes TransStamp Locking and Record Serial 

Numbers (RSNs). Within the RSN description, update the 

topic "Definition" by replacing its second paragraph with the 

following: 

RSNs begin at 1 for each data set and increase by 1 

each time a record is created, regardless of whether 

the transaction creating the record is successful. 

Internally, RSN is stored as a single word. The word is 

diveded into two parts - the integer part (bit 38 - 0) and 

the overflow part (bit 47 - 39). 

When RSN is less than 2**39, it is stored as an Integer. 

If RSN is equal to or greater than 2**39, then bit 47 to 39 

contain the quotient of the RSN divided by 2**39, 

and the arithmetic remainder is stored in the lower 39 

bits. 

The algorithm of assigning the RSN value is demostrated 

with the following ALGOL code. 

DEFINE 

6875 9497–003 61


RSN_OVFLF = [47: 9] #, 

RSN_INTEGERF = [38:39] #, 

UNDEFINED = REAL(NOT FALSE)#, 

BUMP_RSN (RSN_VALUE) = 

BEGIN 

IF RSN_VALUE.RSN_INTEGERF = UNDEFINED.RSN_INTEGERF THEN 

BEGIN 

RSN_VALUE.RSN_INTEGERF := 0; 

RSN_VALUE.RSN_OVFLF := RSN_VALUE.RSN_OVFLF + 1; 

END 

ELSE 

RSN_VALUE.RSN_INTEGERF := 

RSN_VALUE.RSN_INTEGERF + 1; 

END#; 

Based on the algorithm, the maximum RSN is 2**48 - 1. 

Applications can use a REAL item to access RSN and 

apply the algorithm to calculate the value. 

In the following ALGOL example, A_RSN simulates an RSN 

retrieved from the database and B_RSN is the calculated 

RSN value. 

DOUBLE B_RSN, P1; 

REAL B, A_RSN, P2; 

B := 2**39; 

A_RSN := 4"010000000003"; 

P1 := (A_RSN.[47:9]) * (B); 

P2 := A_RSN.[38:39]; 

B_RSN := P1 + P2; 


Allow To Set The Memory Resident For All Sets To Coarse 

SYMPTOMS: 

DASDL will be able to set the MEMORY RESIDENT to COARSE for SET 

in the DEFAULT section. 

Use VDBS STRUCTURE CHANGE command to set the MEMORY RESIDENT 

to COARSE for all index sequential sets of the database. 


Please update the Enterprise Database Server for Clearpath MCP Data 

and Structure Definition Language(DASDL) Programming Reference Manual 

(8600 0213-411) under the Specifying Defaults section under the 

road diagram, please between DUMPSTAMP and 

SECURITY GUARD: 

62 6875 9497–003

-| 

| 

| 

| 

| 

| 

|--/1\-MEMORY RESIDENT = ------ALL-----------| 

| |--COARSE--------| 

| 



Utilities Operations Guide)8600 0759-613) under the Communicating 

with the Database section under the STRUCTURE CHANGE Command section: 

Change the railroad diagram of the STRUCTURE 

---STRUCTURE----*-------()-------------------------- 

| | 

|-SETS--| 

| -




SYMPTOMS: 












| |--COARSE--------| 

| 





---STRUCTURE----*-------()---------------------------| 

| | | 

|-SETS--| | 

| -


Add the following section after MEMORY RESIDENT = RESET, page 12-33 

before the Examples section. 

SETS (MEMORY RESIDENT = COARSE) 

Informs the Accessroutines to employ MEMORY RESIDENT mechanism on 

a structure. Setting MEMORY RESIDENT to COARSE for all INDEX 

SEQUENTIAL setS in the database." 

Add the under the Examples section after the Example 3. 

"Example 4 

The following example changes the MEMORY RESIDENT option of all 

index sequential sets in the database to COARSE. 

2291 SM STRUCTURE SETS (MEMORY RESIDENT = COARSE) 

Component: AUDITLIB PRI-11462553 

Correct Logic for Sequential Read Audit While in Use by DB 

SYMPTOMS: 

When a program used DMAUDITLIB sequential to read an audit while 

the file was still in use by database, then the program could 

not read further once the EOF was hit even though the audit 

file was still extended continuously by database activities. 


The following paragraph should be appended in the description of 

error results under value 17 at page 18-25 of the Entrerprise 

Database Server for Clearpath MCP Utilities Operation Guide( Form 

8600 0759-612): 

For AUDIT_NEXT_RECORD/AUDIT_NEXT_ABSN on an audit which is in use 

by a database, the pointer will stay there. If the audit is 

extended due to the database activities, then the next 

AUDIT_NEXT_RECORD/AUDIT_NEXT_ABSN will resume the read from where 

it stayed. 

6875 9497–003 65


Component: COPYAUDIT PRI-11419500 

Document Tapeset Errors In Utilities Operations Guide 

SYMPTOMS: 

Some tapeset related errors are not documented in the 

Utilities Operations Guide. 


Please make the following changes in Utilities Operations Guide 

(form 8600 0579-612). 

Add the following in Appendix C. COPYAUDIT Errors 

ERROR 121: READPOSITION ERROR ON QUICKCOPY TAPE FILE 

An error occurred while getting the position on the tape. 

This error message indicates a nonfatal problem. 

COPYAUDIT can still position the tape by doing rewinds. 

ERROR 122: LOCATEBLOCK ERROR ON QUICKCOPY TAPE FILE 

An error occurred while locating a block on the QUICKCOPY tape. 

ERROR 124:SYNTAX : TAPESET NUMBER MUST BE BETWEEN 1 AND 9999 

A syntax error exists in your COPYAUDIT statement. 

The valid tapeset numbers are range from 1 to 9999. 

Refer to Section 9 for the COPYAUDIT syntax diagrams. 

ERROR 125: SYNTAX : TAPESET NUMBER ONLY ALLOWED 

FOR VERIFY OR QUICKCOPY COMMAND 

Tapeset number can only be specified for VERIFY or QUICKCOPY 

command. 

ERROR 126: SYNTAX : TAPESET SPECIFICATION NOT ALLOWED 

Tapeset specification is only allowed for VERIFY OR QUICKCOPY 

command. 

ERROR 127: SYNTAX : TAPESET NUMBER REQUIRED 

Tapeset number is missing in the tapeset specification. 

ERROR 128: SYNTAX : MCP DOES NOT SUPPORT LOCATE FAST ACCESS. 

TAPESET SPECIFICATION NOT ALLOWED 

You cannot use the tapeset specification since MCP does not 

support locate fast access. 

ERROR 129: SYNTAX : MCP DOES NOT SUPPORT ASSOCIATEDFILENAME. 

TAPESET SPECIFICATION NOT ALLOWED 

You cannot use the tapeset specification since MCP does not 

support ASSOCIATEDFILENAME tape attribute. 

ERROR 131: TAPESET NUMBER MUST BE LESS THAN OR EQUAL TO AUDIT FILE 

NUMBER 

66 6875 9497–003


The tapeset number specified is greater than the audit file 

number specified for copy operation. 

ERROR 132: TAPESET NUMBER MUST BE LESS THAN AUDIT FILE NUMBER FOR 

QUICKCOPY APPEND COMMAND 

The tapeset number specified is greater than or equal to the 

audit file number specified for append operation. 

ERROR 235: SYNTAX : INVALID ENCRYPT TYPE 


You designated an invalid algorithm type. 

Refer to Section 9 for the COPYAUDIT syntax diagrams. 

ERROR 237: SYNTAX : AUDITENCRYPT OPTION ALLOWD ONLY 

FOR QUICKCOPY TAPE 


You must use QUICKCOPY when specifying AUDITENCRYPT. 

ERROR 238: ERROR IN TAPE ENCRYPTION 

An error occurred during the tape encryption. 

ERROR 239: ERROR CODES TRANSLATION FAILED 

An error occurred during the translation of the 

encryption/decryption error. 

ERROR 240: ERROR IN TAPE DECRYPTION 

An error occurred during the tape decryption. 

ERROR 241: WARNING:EXCLUSIVE OPTION IGNORED FOR TAPE AUDIT 

The EXCLUSIVE option is ignored if the input audit file is on 

tape. 

This error message indicates a nonfatal problem. 

Component: COPYAUDIT PRI-11444857 

OVERRIDE Option For QUICKCOPY From Tape/Tapeset To DISK 

SYMPTOMS: 

The OVERRIDE option is not required when copying audit files from 

TAPE or TAPESET to DISK using the QUICKCOPY command. 


Please make the following changes in Utilities Operations Guide 

(form 8600 0759-612). 

Add the following as the last paragraph under OVERRIDE Option 

in Section 9. 

The OVERRIDE option is not required when copying audit 

files from TAPE or TAPESET to DISK using the QUICKCOPY 

command. 

6875 9497–003 67


Component: DASDL PRI-11498779 


SYMPTOMS: 












| |--COARSE--------| 

| 





---STRUCTURE----*-------()---------------------------| 

| | | 

|-SETS--| | 

| -









"Example 4 




Component: DASDL PRI-11540856 


SYMPTOMS: 












| |--COARSE--------| 

| 





6875 9497–003 69


---STRUCTURE----*-------()---------------------------| 

| | | 

|-SETS--| | 

| -







| |--COARSE--------| 

| 





---STRUCTURE----*-------()---------------------------| 

| | | 

|-SETS--| | 

| -


Component: PROPERTIES PRI-11540864 

-| 

| 

| 

| 

| 

| 


SYMPTOMS: 












| |--COARSE--------| 

| 





---STRUCTURE----*-------()-------------------------- 

| | 

|-SETS--| 

| -


to all index sequential set in the database and a correspoding 

parameter list except for SETS which is only allowed for MEMOry 

RESIDENT option. Each parameter list is applies only to the ....". 








"Example 4 





Problems with SYSTEM/DMDUMPDIR Documentation 

SYMPTOMS: 

There are 2 problems with the documentation in the Enterprise Database 

Server for Clearpath MCP Utilities Operation Guide, Section 6 - 

Backing Up A Database. 

1. Nowhere does it mention that the database must be down to do the 

DMDUMPDIR ENABLE or DISABLE commands. They will wait for CONTROL file 

access if the database is up. 

2. The documentation for the DISABLE command is: 

"DISABLE Command 

Use the DISABLE command to disable the dump directory for a database. 

All available files associated with the dump tape directory, including 

the main directory and all dump directories, are deleted. 

If you use the NOW or option, the database stack 

discontinues and you must run recovery." 

However, nowhere else are the NOW or options mentioned and 

they are not included in the DMDUMPDIR command flow chart, so it is 

impossible to know how to use them. 

6875 9497–003 73



In Section 6 (Backing up a Database) of the Utilities Operations 

Guide (8600 0759-614), add the following text in both subsections 

of ENABLE Command and DISABLE Command of DMDUMPDIR Program section 

(page 6-69 and 6-70): 

DMSQL 

Note: The database cannot be in use when the control file program 

updates the control file. 

Move the following text from section 6 (Backing up a Database) of 

the Utilities Operations Guide (8600 0759-614), under DISABLE 

Command 

subsection (page 6-70) of DMDUMPDIR Program section to DMUTILITY 

DISABLE/ENABLE Statement section (page 11-55) of section 11 

(Checking Integrity of Performance), below the Syntax railroad 

diagram at the end of the page: 

If you use the NOW or option, the database stack 

discontinues and you must run recovery. 

Component: DMSQL PRI-11428908 

Some of the documented NA commands are not supported by 

DMSQL. 

SYMPTOMS: 

The NA commands using the NET and TRACE ALL syntax 

return the error "Invalid option for DMSQL". 


In the section "SQL Query Processor Server Administration" of the 

document "SQL Query Processor for ClearPath MCP Installation and 

Operations Guide" 

On page number 5-6: 

Remove the NET option from the HELP system command. It is not 

supported by DMSQL. 

On page number 5-6 in the last paragraph: 

Remove the "specifying network options" as network options 

is not supported by DMSQL. 


The ALL element should be moved and placed as an alternative to 

the in the main syntax. 


Remove the syntax and associated entries from the table. 

74 6875 9497–003

Add a DEBUG option in its place in the syntax diagram. 


On page number 5-14 in the table of elements, add a DEBUG element: 

Include the following definition "DEBUG option is only available 

when running the DIAGNOSTIC version of the software. The resulting 

trace information is designed to assist Unisys personnel in 

diagnosing problems." 

Component: DMSQL PRI-11450504 

Modify Documentation for Database Update Requirements 

SYMPTOMS: 

Documentation for "Updating Enterprise Database Server Databases 

with Sql Queries" needs changes. 

1) Third bullet about Read-only access control should be changed 

from set to reset. 

2) Fourth bullet about Enterprise Application Environment needs 

clarification. 


Modify the "Updating Enterprise Database Server Databases 

with Sql Queries" sub section in Section 2 of the 

SQL Query Processor for ClearPath MCP Installation and 

Operations Guide (3850 8206). 

In the second bullet about Read-only access, change 

"Read-only access control option set." to 

"Read-only access control option reset." 

In the fourth bullet about Enterprise Application Environment 

databases, replace the existing text with the following: 

Although updates to an EAE database can be performed through 

DMSQL, such direct updates are not recommended as these could 

violate EAE application business rules and could potentially 

corrupt the application integrity of an EAE system. 

Component: RDC PRI-11410596 

Modify SQL Database Text Addition Needed for Relational Design 

Center. 

SYMPTOMS: 

Modify SQL Database option doesn't appear when SQL database is 

right-clicked 

6875 9497–003 75



In the Help Topics area, under the "Working with Databases" 

area, "Modifying an SQL Database" between the first and the 

second steps, please add the following item: 

2. If the database is not yet open, click on Open Database 

to open the database for modification. 

Also, please change the numeral for the second item from 2 to 3 

since this adds an extra step. Also, please change "want" to 

"would like" in step 1. 

In other words, here is the original text: 

Perform the following steps to modify an SQL database: 

1. From the tree view, expand the server containing the 

database you want to modify. 

2. Right-click the database and click Modify SQL Database. 

Here is the suggested changed text: 



database you would like to modify. 




---------------------------------------------------------------- 

On page 4-38, of the SQL Query Processor for ClearPath MCP 

Installation and Operations Guide (3850 8206-000), the following 

item should be added to the "Modifying an SQL Database" section 

between the first and the second steps: 



Also, please change the numeral for the second item from 2 to 3 

since this adds an extra step. Also, please change "want" to 

"would like" in step 1. 

In other words, here is the original text: 



database you want to modify. 


Here is the suggested changed text: 



database you would like to modify. 




---------------------------------------------------------------- 

76 6875 9497–003

DSS 

Component: LIO PRI-11498060 

Deimplement FTAM Attributes 



The FTAM file attributes CREATEPASSWORD, DOCUMENTTYPE and 

PERMITTEDACTIONS together with the associated disk file header 

attributes DFHDOCUMENTTYPE, DFHDOCUMENTTYPEPARAMS and 

DFHPERMITTEDACTIONS have been deimplemented. 

In the File Attributes manual (86000064-511) delete references 

to CREATEPASSWORD, DOCUMENTTYPE and PERMITTEDACTIONS. 

In Table C-1 of the I/O Subsystem manual (86000056-411) delete 

references to DFHDOCUMENTTYPE, DFHDOCUMENTTYPEPARAMS and 

DFHPERMITTEDACTIONS. 

In Table 4-2 of the Getstatus/Setstatus manual (86000346-412) 

replace the description mask bit [44:01] by "Reserved.". 

Component: NFT PRI-11441670 

Minor Improvements to NFT 


Make changes to the "Distributed System Services Operations Guide" 

as follows. 

Under "Sources of information on Installing DSS Providers" in the 

"Installing DSSs" section, make the following changes. 

Add the following notes to the first bullet item -- "You install 

Host Services and NFT ...": 

Note: If the release level of the DSSSUPPORT library is not the 

same as the release level of the MCP then the NFT restart or 

resume function may not work correctly. 

Note: The 54.1 DSSSUPPORT uses a new version (541) for 

FTRECOVERY 

files instead of the old version (1). If you attempt to do an 

NFT Restart on a level 54.1 or newer level system with an 

FTRECOVERY file generated by a 53.1 or older level system, NFT 

will re-copy all the files from the start. If you attempt to do 

an NFT Restart on a level 53.1 or older level system with an 

FTRECOVERY file generated by a 54.1 or newer level system, NFT 

will re-copy all the files from the start. 

6875 9497–003 77


In the "Native File Transfer (NFT)" section make the following 

changes. 

DUMPALL 

Add the following new bullet item to the first "paragraph": 

.File transfers from Library Maintenance CDs 

Change the name of the "Using WFL Commands to Run NFT" subsection 

to: 

Using WFL Statements to Run NFT 

Change the fourth bullet item under "Explanation" in this 

sub-section as follows -- add CDs: 

If you use tapes or CDs as sources, you must specify a single 

destination volume. 

Component: DUMPALL PRI-11498051 














78 6875 9497–003

DUMPANALYZER 

Component: DUMPANALYZER PRI-11266371 

Update ASDNUMBER Command 



The ASDNUMBER (Actual Segment Descriptor Number) command has been 

enhanced to provide additional information. 

The Dumpanalyzer Help command is updated as follows: 

ASDNUMBER (ASD) 

ASDnumber-----------------------------------------------------------| 

| | |------------| 

| | 

|-EXPAND-| 

| | 

|-RAW----| 

>-----------------| 

|


When an ASD number, a range of ASD numbers, or a stack number is 

specified, the ASD entries in that range are examined, where the 

stack number option implies all ASD entries with an ASD owner stack 

matching the input stack number. The default ASD selection is the 

range including ASD 1 through the maximum ASD number used at the 

time of the dump (see 'Max ASD index used' in HEADING output). 

The range of ASD entries will be printed if an output format of RAW 

or EXPAND is used. The default output format is EXPAND. 

If one or more ASD filters is specified, then only ASDs for the ASD 

range or owner stack number that meet the filter criteria are 

printed and/or summarized. The ASD filters are: 

AVAIL: Include ASD entries that have an avail ASD1 TAG 

INUSE: Include ASD entries that have an inuse ASD1 TAG 

PRESENT: Include ASD entries with segments present in memory 

ABSENT: Include ASD entries with segments absent from memory 

LOCKED: Include ASD entries that are LOCKED or BUSY 

VIRGIN: Include ASD entries that are marked as VIRGIN 

MASK: Include ASD entries with ASD4 matching the current 

global MASK and PATTERN setting 

The USAGE option presents summary information about the select ASD 

table range or owner stack in a tabluar report. By default, the 

ASD entries are not expanded. To print the individual ASD entries 

that are included in the summary, the RAW or EXPAND output option 

must be specified. Note that the USAGE option may take significant 

processing time to complete. 

Please update the System Software Utilities Operations Reference 

Manual, Dumpanalyzer Chapter, Dumpanalyzer Commands Section, 

ASDNUMBER (Actual Segment Descriptor Number) command as follows: 

o Replace the Syntax diagram as follows: 

ASDnumber-----------------------------------------------------------| 

| | |------------| 

| | 

|-EXPAND-| 

| | 

|-RAW----| 

>-----------------| 

80 6875 9497–003

|


(FIBMARK) 1352 146 0 0 

(SEGDOPE) 695 88 0 0 

(SEGSEG) 13453 106753 0 0 

(TABMARK) 988 162 0 0 

(DOPEVECT) 8153 1695 0 0 

(IOCBAREA) 5718 336 0 0 

(DIRECTIOBUFF) 3499 8615 0 0 

(EVENTARRAY) 609 267 0 0 

(DIRECTIOBUFFTOBE) 0 0 2531 2338 

(STACK) 791 1965 0 0 

(SIBMARK) 23 2 0 0 

(PIBMARK) 802 153 0 0 

(BUFFERHEADER) 661 8 0 0 

(STRUCTURED) 11092 1353 0 0 

(SUBSPACE_ARRAY) 58 9751 0 0 

(MESSAGEAREA) 2078 84 10724 188 

(IOCDAREA) 3499 76 0 0 

(CODEAREA) 15556 5192 27752 5529 

(INSTACKAREA) 169 3 0 0 

(ICMMARK) 111 3 0 0 

(PERMSAVEAREA) 811 1924 0 0 

(LOGICALIOBUFF) 520 1389 0 0 

(EVENTCONTAINER) 594 68 0 0 

(DOPEOREVENTAREA) 1648 68 0 0 

(EVENTSEG) 11 88 0 0 

(MULTIAREABUFFER) 5155 4930 0 0 

(RESERVEAREA) 16 9 0 0 

(EVENTMESSAGEAREA) 18 1 0 0 

(IOCBMESSAGEAREA) 602 36 0 0 

(MCBAREA) 2722 405 0 0 

(EVSTATEAREA) 33243 423 0 0 

---------------------------------------- 

Totals: 364957 189302 54268 11043 

Present overlay: 240977 144654 0 0 

Virgin ASDs: 0 0 43544 10856 

Available ASDs: 51181 

ASDs Examined: 470406 

Total ASD count: 2762997 


Introduce Options To The LINKCHECK Command 

SYMPTOMS: 

In addition to validating the memory links associated with 

in-use and available memory area, Dumpanalyzer's LINKCHECK 

command validates several other aspects of memory management. 

The LINKCHECK command may take a significant amount of time to 

complete, especially when analyzing dumps from large memory 

configurations. Occasionally it is desirable to only validate 

82 6875 9497–003

a specific aspect of memory management covered by the 

LINKCHECK command. 



The LINKCHECK command now accepts several options, allowing 

Dumpanalyzer to validate specific aspects of memory 

management. 

The LINKCHECK command now accepts several options: 

|-------------------| 

V | 

LINKCHECK --------------------------------------| 

| | 

|-- ALL ------| 

| | 

|-- LINKS ----| 

| | 

|-- LISTS ----| 

| | 

|-- MEMTOSS --| 

| | 

|-- WSLRU ----| 

LINKCHECK 

LINKCHECK ALL 

The LINKCHECK command works as before if no option or the ALL 

option is specified. All validation is performed. 

LINKCHECK LINKS 

When the LINKS option is specified, the LINKCHECK command only 

validates the link words associated with each inuse and 

available memory area. 

LINKCHECK LISTS 

When the LISTS option is specified, the LINKCHECK command only 

validates the MCP's available memory lists. 

LINKCHECK MEMTOSS 

When the MEMTOSS option is specified, the LINKCHECK command 

only validates the MCP's Top of Save Memory Pointers. 

LINKCHECK WSLRU 

When the WSLRU option is specified, the LINKCHECK command only 

validates the MCP's Working Set Least Recently Used list. 

6875 9497–003 83



Introduce New SUMMARY Option Of LANGUAGE 


The SUMMARY command now recognizes LANGUAGE as a new summary 

item. When the LANGUAGE option is specified, the SUMMARY 

command displays the name of the compiled language for code 

files. 

In the ClearPath MCP System Software Utilities Operations 

Reference Manual (8600 0460-512): 

Section 8. DUMPANALYZER 

DUMPANALYZER Commands 

SUMMARY (Summarize Stack Information) 

Please add the LANGUAGE option to the railroad 

diagram: 

|-- LANGUAGE ---------------| 

Under the Explanation section, please add the following entry 

to the table of descriptions: 

+--------------+-----------------------------------+ 

| Specify... | To Display... | 

+--------------+-----------------------------------+ 

| LANGUAGE | The object code file language of | 

| | each process. | 

+--------------+-----------------------------------+ 


Convert Code Address Into Sequence Number 

SYMPTOMS: 

There is no Dumpanalyzer command to convert an arbitrary display 

form code address into its corresponding sequence number. 


Dumpanalyzer now provides command options to convert a display form 

code word into a sequence number, where the display form consists 

of an SDI (segment dictionary index), PWI (program word index) and 

PSI (program syllable index), represented in the format 

SDI:PWI:PSI. 

Specifically, the WHO command is enhanced to provide analysis of 

MCP code pointers, while the new command, RCWTOSEQ may be used to 

84 6875 9497–003

convert any USER or MCP arbitrary code address into its 

corresponding sequence number. 


The WHO command now allows conversion of a code address of the 

form SDI:PWI:PSI into a sequence number. The command has also been 

extended to analyze PCW words for a segment in order to display the 

sequence numbers for each PCW in the segment using the command 

option ":EX". 

The RCWTOSEQ command is added mainly to allow analysis of USER code 

pointers, and requires the user to specify the segment dictionary 

stack and supply a codefile compiled with LINEINFO. 

The following documentation should be included in the System 

Software Utilities Operations Reference Manual, DUMPANALYZER 

section, DUMPANALYZER Command topics for the new RCWTOSEQ command 

and the enhanced WHO command. 

RCWTOSEQ (Convert RCW Into Sequence Number) 

RCWTOSEQ converts a display form, or diagnostic RCW (SDI:PWI:PSI) 

into a sequence number using the LINEINFO from a codefile. The 

command requires the physical codefile associated with a segment 

dictionary stack in order to determine the sequence number. The 

segment dictionary stack number is entered using either MCP or a 

indicating a stack or ASD number from which the segment 

dictionary will be derived. If the number is a process stack, the 

code stack will be determined from its PIB CODELINKS word. If the 

number is a segment dictionary stack, it is used directly. If the 

number is a code segment ASD, its ASD Mom Reference is used to 

derive the segment dictionary stack and SDI. Finally, if MCP is 

specified instead of a number, the analyzed MCP codefile will be 

used. Note that the WHO command may be used when analyzing MCP 

code pointers. 

Once the physical codefile is located, the creation timestamp is 

compared against the codefile header value from the dump. If the 

physical codefile does not match the version in use at the time of 

the dump, or the codefile cannot be located, the user will be 

prompted to acknowledge use of the codefile or to specify a new 

codefile to use. Once a codefile has been accepted, it will be 

remembered as if a CODEFILE command had been previously used. This 

process is used to make sure the user has been warned that the 

codefile being used may not match the one running at the time of 

the dump, and the results may be incorrect. Note that the CODEFILE 

command may be used prior to using the RCWTOSEQ command to avoid 

prompting the user for acceptance of the file to use. 

Syntax 

RCWTOSEQ-------------------------------------! 

! ! ! ! ! ! ! 

!- STACK ! ! !- : -! !- : -! 

! ! ! ! 

!- STK ---! ! ! 

6875 9497–003 85


Examples 

! ! ! 

!- MCP --------------! ! 

! ! 

!---------------------! 

! ! 

!- ASD -! 

INPUT: RCW 72C0 3:110A:2 

Segment Dictionary Stack 072C0 *SYSTEM/DUMPANALYZER/541 ON DISK. 

Creation Timestamp: Mon, Jun 9, 2008 14:33:41 

Stack 072C0 Segment @ 0003:110A:2 (99912100) 

INPUT: RCW MCP 1007:1AB:0 

Segment Dictionary Stack 00012 *SYSTEM/MCPE/54126/C ON SYSTEM. 

Creation Timestamp: Wed, Jun 4, 2008 14:08:56 

1007:01AB:0 (15427780/05174513) RESIZEANDDEALLOCATEGUTS 

01C2 (PCW) RESIZEANDDEALLOCATEGUTS 

7 C00CAA 101061 ASD=000830E, LL=1, Control State, MCP 

Segment @ 1007:0065:2 (05173626) RESIZEANDDEALLOCATEGUTS 

1007 (SEG) C C80000 001061 Desc [Present-mom]: ASD=000830E, 

Address=0001826150, Length=4621, Readonly (PERMSAVEAREA) 

WHO (Show D[0] Global Identifier) 

The WHO command displays the global identifier for the specified D[0] 

offset (cell). An outer-block procedure PCW is shown as SDI:PWI:PSI 

from the D[0] stack image. For an outer-block procedure code 

segment, the names, PCW D[0] offsets, and PCW are shown for all 

procedures in that segment. 

When the ":EX" option is included, additional analysis is provided 

for the stack cell. 

When the additional numbers are provided, the input is treated as 

a code pointer which is converted into its corresponding sequence 

number. 

All aliases for MCP stack cells are retained and are returned by the 

WHO command. 

Syntax: 

WHO-- ----------------------------------------------! 

! ! ! ! 

!------ ------- -! !- :EX -! 

! ! ! ! 

!- : -! !- : -! 

Examples: 

INPUT: WHO 1007 


86 6875 9497–003



:0000:0 (PCW @10F0) DM_RESIZE LENGTH = 57 

:0039:0 (PCW @0062) RESIZEANDDEALLOCATE LENGTH = 44 

:0065:2 (PCW @01C2) RESIZEANDDEALLOCATEGUTS LENGTH = 4520 

INPUT: WHO 1007:EX 




7 C00000 101061 ASD=000830E, LL=1, Normal State, MCP 

Segment @ 1007:0000:0 (05168955) DM_RESIZE 



Segment @ 1007:0039:0 (05169250) RESIZEANDDEALLOCATE 


7 C00CAA 101061 ASD=000830E, LL=1, Control State, 

MCP Segment @ 1007:0065:2 (05173626) RESIZEANDDEALLOCATEGUTS 

INPUT: WHO 1007:1AB:0 


INPUT: WHO 1007:1AB:0:EX 








Convert Code Address Into Sequence Number 

SYMPTOMS: 

There is no Dumpanalyzer command to convert an arbitrary display 

form code address into its corresponding sequence number. 


Dumpanalyzer now provides command options to convert a display form 

code word into a sequence number, where the display form consists 

of an SDI (segment dictionary index), PWI (program word index) and 

PSI (program syllable index), represented in the format 

SDI:PWI:PSI. 

Specifically, the WHO command is enhanced to provide analysis of 

MCP code pointers, while the new command, RCWTOSEQ may be used to 

convert any USER or MCP arbitrary code address into its 

corresponding sequence number. 

The WHO command now allows conversion of a code address of the 

form SDI:PWI:PSI into a sequence number. The command has also been 

extended to analyze PCW words for a segment in order to display the 

6875 9497–003 87


sequence numbers for each PCW in the segment using the command 

option ":EX". 

The RCWTOSEQ command is added mainly to allow analysis of USER code 

pointers, and requires the user to specify the segment dictionary 

stack and supply a codefile compiled with LINEINFO. 

The following documentation should be included in the System 

Software Utilities Operations Reference Manual, DUMPANALYZER 

section, DUMPANALYZER Command topics for the new RCWTOSEQ command 

and the enhanced WHO command. 

RCWTOSEQ (Convert RCW Into Sequence Number) 

RCWTOSEQ converts a display form, or diagnostic RCW (SDI:PWI:PSI) 

into a sequence number using the LINEINFO from a codefile. The 

command requires the physical codefile associated with a segment 

dictionary stack in order to determine the sequence number. The 

segment dictionary stack number is entered using either MCP or a 

indicating a stack or ASD number from which the segment 

dictionary will be derived. If the number is a process stack, the 

code stack will be determined from its PIB CODELINKS word. If the 

number is a segment dictionary stack, it is used directly. If the 

number is a code segment ASD, its ASD Mom Reference is used to 

derive the segment dictionary stack and SDI. Finally, if MCP is 

specified instead of a number, the analyzed MCP codefile will be 

used. Note that the WHO command may be used when analyzing MCP 

code pointers. 

Once the physical codefile is located, the creation timestamp is 

compared against the codefile header value from the dump. If the 

physical codefile does not match the version in use at the time of 

the dump, or the codefile cannot be located, the user will be 

prompted to acknowledge use of the codefile or to specify a new 

codefile to use. Once a codefile has been accepted, it will be 

remembered as if a CODEFILE command had been previously used. This 

process is used to make sure the user has been warned that the 

codefile being used may not match the one running at the time of 

the dump, and the results may be incorrect. Note that the CODEFILE 

command may be used prior to using the RCWTOSEQ command to avoid 

prompting the user for acceptance of the file to use. 

Syntax 

RCWTOSEQ-------------------------------------! 

! ! ! ! ! ! ! 

!- STACK ! ! !- : -! !- : -! 

! ! ! ! 

!- STK ---! ! ! 

! ! ! 

!- MCP --------------! ! 

! ! 

!---------------------! 

! ! 

!- ASD -! 

88 6875 9497–003

Examples 


INPUT: RCW 72C0 3:110A:2 

Segment Dictionary Stack 072C0 *SYSTEM/DUMPANALYZER/541 ON DISK. 

Creation Timestamp: Mon, Jun 9, 2008 14:33:41 

Stack 072C0 Segment @ 0003:110A:2 (99912100) 

INPUT: RCW MCP 1007:1AB:0 

Segment Dictionary Stack 00012 *SYSTEM/MCPE/54126/C ON SYSTEM. 

Creation Timestamp: Wed, Jun 4, 2008 14:08:56 







WHO (Show D[0] Global Identifier) 

The WHO command displays the global identifier for the specified D[0] 

offset (cell). An outer-block procedure PCW is shown as SDI:PWI:PSI 

from the D[0] stack image. For an outer-block procedure code 

segment, the names, PCW D[0] offsets, and PCW are shown for all 

procedures in that segment. 

When the ":EX" option is included, additional analysis is provided 

for the stack cell. 

When the additional numbers are provided, the input is treated as 

a code pointer which is converted into its corresponding sequence 

number. 

All aliases for MCP stack cells are retained and are returned by the 

WHO command. 

Syntax: 

WHO-- ----------------------------------------------! 

! ! ! ! 

!------ ------- -! !- :EX -! 

! ! ! ! 

!- : -! !- : -! 

Examples: 

INPUT: WHO 1007 






INPUT: WHO 1007:EX 

6875 9497–003 89






Segment @ 1007:0000:0 (05168955) DM_RESIZE 



Segment @ 1007:0039:0 (05169250) RESIZEANDDEALLOCATE 


7 C00CAA 101061 ASD=000830E, LL=1, Control State, 

MCP Segment @ 1007:0065:2 (05173626) RESIZEANDDEALLOCATEGUTS 

INPUT: WHO 1007:1AB:0 


INPUT: WHO 1007:1AB:0:EX 








PBTUNLOAD Option To Unload Single-File Printer Backup Tape 

SYMPTOMS: 

It is not possible to specify that printer backup tapes 

being created should be unloaded when the printer file is closed. 


A new system option, PBTUNLOAD (42), has been implemented 

in order to allow an installation to specify that each printer 

backup file should be on a separate tape volume. 

If this option is enabled (OP + PBTUNLOAD), printer backup tapes 

being created are unloaded when the file is closed. Thus, 

each printer backup tape file requires a separate tape volume. 

If this option is disabled (OP - PBTUNLOAD), printer backup tapes 

being created are left uptape when the file is closed. Thus, 

multiple printer backup tape files can be written to the 

same tape volume. 

The previous behavior was that of the option being disabled; 

that is, multiple printer backup tape files can be 

written to the same tape volume. 

90 6875 9497–003


Analyze Coremap File Without Memory Dump 


SYMPTOMS: 

Dumpanalyzer's COREMAP (Memory Analysis) command cannot 

provide detailed memory information solely from a COREMAP data 

file. 

After initially generating its data file, most COREMAP 

commands do not require information in the memory dump to 

provided detailed memory usage information. 


Dumpanalyzer can now analyze the memory usage information in a 

COREMAP file without the corresponding memory dump. 

RUN $SYSTEM/DUMPANALYZER;FILE COREMAP= 

COREMAP GLOBALS does not work... 

In the System Software Utilities Operations Reference Manual 

(8600 0460-512), Section 8. DUMPANALYZER: 

Add the following under the section: 

General Information 

DUMPANALYZER Files 

COREMAP 

You can file-equate the COREMAP file if you wish to analyze 

a COREMAP data file without its corresponding memory dump. 

For example: 

FILE COREMAP=MEMDUMP/COREMAP/112108/1700 ON DUMPS 

When you run DUMPANALYZER using this method, DUMPANALYZER 

only recognizes a limited number of commands, such as the 

COREMAP command and commands that control output. 

6875 9497–003 91



ACTUALMYNAME File Attribute 

SYMPTOMS: 

The port number assigned by TCPIP to a port file cannot be 

determined. 


ACTUALMYNAME is a new readonly subport File Attribute. If the 

MYNAME port File Attribute is a null string and the service is 

TCPIPNATIVESERVICE then the port number assigned by TCPIP is 

returned. In all other cases the vale of the MYNAME attribute is 

returned. 

Add this description of the attribute to the File Attributes manual 

(86000064-511) : 

ACTUALMYNAME 

Kinds Port 

Interrogate Anytime 

Modify Never 

Type Character string 

Range Not applicable 

Default Not applicable 

Abstract Value Not applicable 

Stored permanently No 

Parameters 1 

Heritage Host Services Logical I/O Not supported 

Port Services All 

If the MYNAME port File Attribute is a null string and the service 

is TCPIPNATIVESERVICE then the port number assigned by TCPIP is 

returned. In all other cases the value of the MYNAME File Attribute 

is returned. 

This attribute requires a subfile index as a parameter. 


FIB Command Now Supports An ALL Stacks Option 


The syntax of the FIB command is extended to accept a value of 

ALL when using the STACK option. 


92 6875 9497–003




FIB (File Information Block) 

Add the ALL option to the SYNTAX diagram as follows: 

FIB----------------- -------| 

| | | 

|-- AT --| | 

| | 

|-- VIA -- ---------| 

| | 

|-- STACK --- ----| 

| | | | 

| |----- ALL --------| | 

| | 

|-- ---------| 

| | 

|-- ----| 

In the explanation section add the following: 

FIB STACK ALL 

Analyzes the FIB for every file opened by all stacks. 


Improvements to PORT analysis 



Update System Software Utilities Operations Reference Manual, 

Section 8 - Dumpanalyzer. 

Update the syntax description for PORT command: 

PORT ----- --------------------------------------! 

! ! ! ! ! 

!--- AT ------! !--- EXPAND ----------! ! 

! ! ! ! ! 

!--- VIA ---! !--- TERSE -----------! ! 

! ! ! ! ! 

!--- ALL ---------------! !--- ONELINE ---------! ! 

! ! ! ! ! 

!--- SERVICE ---! !--- NOSUBPORTS ------! ! 

! ! ! ! 

! !--- SUMMARY ---------! ! 

! ! ! ! 

6875 9497–003 93


! !--- SUMOFFER --------! ! 

! ! 

!--- PROVLIST ----- ----------------------! 

! ! 

!--- AT ------! 

! ! 

!--- VIA ---! 

Following the description for PORT ALL add: 

PORT SERVICE 

Analyzes all the port structures assigned to the specified 

Service and their subport structures, depending upon the level of 

subport detail requested. A unique service number exists for 

each network type. For example, the service number for BNA is 

zero (0), the service number for TCP protocol is is twelve (12). 

The value of the service number is specified using the basic 

NUMBER construct, i.e. the default is a . 

To select TCP PORT files, use "SERVICE C". 

Following the description for PORT NOSUBPORTS add: 

PORT ALL SUMMARY 

PORT SERVICE SUMMARY 

PORT ALL SUMOFFER 

PORT SERVICE SUMOFFER 

SUMMARY and SUMOFFER provide a single line summary for each PORT, 

containing the maximum subports declared, and the number of open, 

closed and allocated subports, and the declaring process 

identity. SUMOFFER includes a count of offered subports. 


Analyze MEMRQ For A Given IOP 

SYMPTOMS: 

The MEMRQ (Memory Result Queue) command requires a hardware 

group parameter. It is the user's responsibility to find the 

hardware group value for the IOP of interest. 


The MEMRQ command now accepts an IOP number parameter. When 

specified, the MEMRQ command will analyze the memory result 

queue associated with the IOP's hardware group. 


(8600 0460-512) update the help text for the MEMRQ command as 

follows: 

94 6875 9497–003



MEMRQ (Memory Result Queue) 


The MEMRQ (Memory Result Queue) command displays information 

describing the state and contents of the Memory Result Queue 

associated with the Hardware Group identified by or 

for the specified IOP. 

-- MEMRQ --- -------------------------------------| 

| | 

|- IOP -| 


System Factors (SF) Command 


In the System Software Utilities Operations Reference Manual (8600 

0460-512) add the SF command as follows: 



SF (System Factors) 

The SF command displays the system factors at the time of the dump 

matching the output produced for the ODT 'SF' command. 

Syntax 

SF -----------------------------------------------------------------| 

Explanation 

The system factors are presented from the memory image being analyzed 

and reflect the values at the time when the memory dump was 

To obtain the specific pragmatics of the data presented, refer to the 

SF command in the System Commands Operations Reference Manual. 

The SF command is not valid for program dump files. 

6875 9497–003 95



System Factors (SF) Command 


In the System Software Utilities Operations Reference Manual (8600 

0460-512) add the SF command as follows: 



SF (System Factors) 

The SF command displays the system factors at the time of the dump 

matching the output produced for the ODT 'SF' command. 

Syntax 

SF -----------------------------------------------------------------| 

Explanation 

The system factors are presented from the memory image being analyzed 

and reflect the values at the time when the memory dump was 

To obtain the specific pragmatics of the data presented, refer to the 

SF command in the System Commands Operations Reference Manual. 

The SF command is not valid for program dump files. 


Add SSL Logical IO Attributes and Errors 

SYMPTOMS: 

Securing a TCPIP connection using SSL is only available using 

a Connection Library interface. This private interface is 

used by FTPSUPPORT, but it is not documented and is difficult 

for programs to use. 


A new interface is now available to secure TCPIP connections 

using SSL. Secure connections are now available to programs 

using TCPIPNATIVESERVICE Port subfiles and is done through 

the use of several new Port subfile attributes. 

New I/O results and Open/Close results have also been added 

to support securing connections. 

96 6875 9497–003


The following text should be added to Section 4 General File 

Attributes N through S. 

SSLSECUREMODE 

============= 

Kind Port subfile 


Modify When closed 

Type Mnemonic 

Default UNSECURE 

Port Service TCPIPNATIVESERVICE 

The SSLSECUREMODE attribute specifies if data is transmitted 

over a secure or non-secure connection. The connection is 

secured using the SSL protocol. 

The following values for SSLSECUREMODE are available: 

Mnemonic Value Value Description 

UNSECURE 0 Connection security is turned off. 

SECURE 1 Connection security is turned on. 

SSLKEYCONTAINER 

=============== 





Default Null string 


The SSLKEYCONTAINER attribute specifies the key container used 

during SSL negotiation. 

SSLCIPHERS 

========== 






6875 9497–003 97



The SSLCIPHERS attribute specifies the allowed ciphers used 

to negotiate an SSL handshake. The attribute is a string 

of cipher values separated by a comma (,). 

For example RSA_Export_With_RC4_40_MD5, 

TLS_RSA_With_AES_CBC_128_SHA. 

The following values for SSLCIPHERS are valid. 

Cipher Values 

RSA_With_NULL_MD5 

RSA_With_NULL_SHA 

RSA_Export_With_RC4_40_MD5 

RSA_With_RC4_128_MD5 

RSA_With_RC4_128_SHA 

RSA_Export_With_RC2_CBC_40_MD5 

RSA_Export_With_DES_40_CBC_SHA 

RSA_With_DES_CBC_SHA 

RSA_With_3DES_EDE_CBC_SHA 

TLS_RSA_With_AES_128_CBC_SHA 

TLS_RSA_WITH_AES_256_CBC_SHA 

TLS_RSA_Exp1024_Wth_DES_CBC_SHA 

TLS_RSA_Exp1024_Wth_RC4_56_SHA 

SSLNEGOTIATEDCIPHER 

=================== 



Modify Never 




The SSLNEGOTIATEDCIPHER attribute specifies the cipher used 

during the secured connection. TCPIP uses the SSLCIPHERS 

attribute to determine the list of available ciphers that 

can be used to secure the connection. TCPIP will negotiate 

with the remote host to decide what cipher each host is 

willing to use. When a cipher has been selected and the 

connection is secured, SSLNEGOTIATEDCIPHER is updated with 

the cipher value. 

The following values for SSLNEGOTIATEDCIPHER are valid. 

Cipher Name 


98 6875 9497–003













SSLROOTSTORE 

============ 








The SSLROOTSTORE attribute identifies the trusted root store 

where trusted certificates are stored. 

If SSLROOTSTORE is null, the default root store "ROOT." is 

used when securing the connection. 

SSLVERSION 

========== 



Modify Never 

Type Mnemonic 

Default Null 


The SSLVERSION attribute displays the protocol version used 

to secure a connection. When a open connection is secured, 

TCPIP updates SSLVERSION with the selected SSL protocol used 

to secure the connection. 

The following values are valid: 


Null 0 The connection is not secure. 

SSL30 768 SSL version 3.0. 

TLS 769 SSL version 3.1. 

6875 9497–003 99


SSLERROR 

======== 



Modify Never 

Type Integer 

Default 0 


Interrogate the SSLERROR attribute to determine the 

SSL error during dialogue establishment and termination. 

SSLERROR is also used to return the reason for 

deactivation of a subfile. 

Interrogate the SSLERROR attribute to also find the 

SSL error returned on a READ or WRITE operation. 

The SSL error description and value are documented in the 

Security SDK. 

SSLTYPE 

======= 




Type Mnemonic 

Default IMPLICIT 


The SSLTYPE attribute specifies whether the connection is 

secured either by an Implicit or Explicit security. 

Implicit security automatically begins with an SSL connection 

as soon as the client connects to a server. Only IMPLICIT 

is supported to secure the connection. 

The following values for SSLTYPE are available: 


IMPLICIT 2 The connection is secured with SSL30. 

100 6875 9497–003


The following text should be added to the SUBFILEERROR attribute 

description in Section 4 General File Attributes N through S. 

SUBFILEERROR (Modified) 

============ 

68 (SSLSESSIONERROR) 

An SSL error has been returned by the TCP/IP Network 

Provider's SSL module. Interrogate the SSLERROR 

attribute to determine the error being sent. 

The following text should be added to Appendix F - I/O 

Enumerated Values. 

171 (SSLIOERROR) 

The READ or WRITE operation failed because the TCP/IP 

Network Provider's SSL module has returned an error. 

Interrogate the SSLERROR attribute to determine 

the error the operation is returning. 

The following text should be added Appendix E - OPEN, CLOSE, 

and RESPOND Results. 

400 (SSLSESSIONERRORRSLT) 






SYMPTOMS: 






6875 9497–003 101










SSLSECUREMODE 

============= 




Type Mnemonic 











=============== 









102 6875 9497–003

SSLCIPHERS 

========== 














Cipher Values 















=================== 



Modify Never 












6875 9497–003 103



Cipher Name 














SSLROOTSTORE 

============ 











SSLVERSION 

========== 



Modify Never 

Type Mnemonic 

Default Null 






104 6875 9497–003







SSLERROR 

======== 



Modify Never 

Type Integer 

Default 0 









Security SDK. 

SSLTYPE 

======= 




Type Mnemonic 








6875 9497–003 105








============ 


















106 6875 9497–003


Introduce New SUMMARY Option Of LANGUAGE 



The SUMMARY command now recognizes LANGUAGE as a new summary 

item. When the LANGUAGE option is specified, the SUMMARY 

command displays the name of the compiled language for code 

files. 





SUMMARY (Summarize Stack Information) 

Please add the LANGUAGE option to the railroad 

diagram: 

|-- LANGUAGE ---------------| 

Under the Explanation section, please add the following entry 

to the table of descriptions: 

+--------------+-----------------------------------+ 

| Specify... | To Display... | 

+--------------+-----------------------------------+ 

| LANGUAGE | The object code file language of | 

| | each process. | 

+--------------+-----------------------------------+ 


New Commands And Options For Memory Pool Diagnostics 



(8600 0460-512): 



Update the following sections: 

o ASDNUMBER (Actual Segment Descriptor Number) 

6875 9497–003 107


Replace Example 1 with the following: 

INPUT: ASDNUMBER 6E949 FOR 2 

ASD1[006E949]:[00001BA524] 8 660026 D259E8 

ASD1_SEGTYPEF = 1 (E-MODE OR BYTE MEMORY) 

ASD1_PRESENTTOPROCF = 1 

ASD1_CODESEGMENTHALTF = 0 

ASD1_NOTSTACKF = 1 

ASD1_ADDRESSVALIDF = 1 

ASD1_READONLYF = 0 

ASD1_ADDRESSF = 0026D259E8 

ASD2[006E949]:[00001BA525] 8 000000 00003C 

ASD2_DONTRESIZEF = 0 

ASD2_VIRGINASDF = 0 

ASD2_NIBBLE_EXCESSF = 0 

ASD2_WORD_DEFICIENCYF = 0000 (0) 

ASD2_SPACEUSAGEF = 00 (NORMALAREA) 

ASD2_LENGTHF = 0003C (60) 

ASD3[006E949]:[00001BA526] D 900052 1019AF 

INDEX = 00521 (1313) 

ASDINDEX = 000CD7C 

ASD4[006E949]:[00001BA527] 0 000000 A00250 

ASD4_LINKASDINDEXF = 0000000 

ASD4_OLAYSTATEF = 5 (PRESENT OVERLAYABLE SEG) 

ASD4_POOLOBJECTF = 1 

POOL LINKA WORD = 3 006E94 901190, OFFSET = 4496 

POOL LINKB WORD = 3 000000 00003E, COREADJ = 62 

POOLAREA ASD = 006568A 

ASD4_HOLDALLPBITSF = 0 

ASD4_OWNERSTACKF = 00012 

ASD4_MARKEDFORWSSHERIFFF = 0 

ASD4_UNLOCKDISPOSALF = 0 

ASD4_LOCKBITF = 0 

TBIT_RCWS[006E949]: 0 055D4F 931532 

DIAG STKNR = 0055D 

DIAG SDI:PWI:PSI = 1532:0F93:2 (04298216/37891080) GET 

ASD LOCK STACK = 0055D 

ASD1[006E94A]:[00001BA528] B 000000 0670E2 

NEXT AVAILABLE ASD = 00670E2 

ASD2[006E94A]:[00001BA529] B 000000 000005 






ASD2_LENGTHF = 00005 (5) 

108 6875 9497–003


ASD3[006E94A]:[00001BA52A] B 006804 431026 

DEALLOCATED @ 1026:0443:0 (24524860/24534200/24584050) BLOCKEXIT 

ASD4[006E94A]:[00001BA52B] B 000000 800D11 


ASD4_OLAYSTATEF = 4 (UNINIT OVERLAYABLE SEG) 







TBIT_RCWS[006E94A]: 0 1F9C4F 931532 

DIAG STKNR = 01F9C 

DIAG SDI:PWI:PSI = 1532:0F93:2 (04298216/37891080) 

GETHEADER 

ASD LOCK STACK = 01F9C 


The following shows the output from the ASD USAGE command. 

INPUT: ASD USAGE 

ASD 0000001 thru 006F54E Usage Summary 

-------------------------------------- 

Addr Valid Kwords PoolObj Kwords 

--------------------------------------------- ... 

NORMALAREA 266,116 47,673 255,221 21,681 

FIBMARK 1,417 153 1,417 153 

SEGDOPE 617 25 613 6 

SEGSEG 1,321 9,978 20 3 

TABMARK 960 161 950 159 

DOPEVECT 9,140 1,729 8,018 306 

IOCBAREA 2,245 132 1,197 71 

DIRECTIOBUFF 3,044 9,587 1,543 513 

EVENTAR 618 252 585 54 

DIRECTIOBUFFTOBE 0 0 0 0 

STACKMARK 839 2,027 194 67 

POOLAREA 4,049 1,046 0 0 

SIBMARK 19 2 0 0 

PIBMARK 868 203 858 200 

BUFFERHEADER 534 6 534 6 

STRUCTUREDAREA 9,289 1,297 9,165 1,289 

SUBSPACE_ARRAY 6,158 12,168 0 0 

MESSAGEAREA 2,524 82 2,520 82 

IOCDAREA 3,041 283 3,041 283 

CODEAREA 15,968 6,271 14,550 2,463 

INSTACKAREA 227 3 0 0 

ICMMARK 111 3 111 3 

6875 9497–003 109


IOBUFFER 482 1,021 0 0 

EVENTCONTAINERAR 692 69 681 58 

DOPEOREVENTAREA 1,453 60 359 15 

EVENTSEG 10 80 0 0 

RESERVEAREA 16 9 0 0 

EVENTMESSAGEAREA 18 1 5 1 

IOCBMESSAGEAREA 310 19 279 17 

MCBAREA 3,294 490 0 0 

EVSTATEAREA 25,814 328 25,610 326 

--------------------------------------------- ... 

Totals 365,125 97,826 329,722 28,381 

Present 

Save segments 119,424 48,153 90,418 7,389 

Overlayable 245,701 49,674 239,304 20,992 

------------------------------------------- 

365,125 97,826 329,722 28,381 

No Memory 

Uninit overlay 641 371 567 121 

OS=0/Virgin 52,795 8,301 213 104 

------------------------------------------- 

53,436 8,671 780 224 

AvailabLe ASDs 

Deallocated 5,292 

Reserved 32,161 

----------- 

37,453 

ASDs Examined 456,014 of 2,742,026 ( 16.63 %) 

PoolObject ASDs 329,722 of 365,125 ( 90.30 %) 

PoolObject KW 28,381 of 97,826 ( 29.01 %) 

Area Reduction 35,403 vs 361,076 ( 90.20 %) 

PoolObject/Area 81.43 in 4,049 PoolAreas 

(Please append the following to the right side of the report) 

No Mem Kwords 

... ------------------- 

13,065 2,848 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

239 299 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

110 6875 9497–003

o CU (Core Utilization) 


10,361 34 

0 0 

29,771 5,491 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

... ------------------- 

53,436 8,671 

Replace the railroad diagram for the CU command with the 

following: 

CU---------------------------------------------------| 

| | | | 

|-- POOLS --| |-- AVAIL ------------------| 

| | 

|-- LISTS ------| 

| | 

|-- OLAYLISTS --| 

| | 

|-- SAVELISTS --| 

| | 

|-- POOLS ------| 

o LINKCHECK (Check Memory Link) 

Add the POOLS option to the LINKCHECK railroad diagram 

and add the description of the POOLS option listed below: 

|-------------------| 

V | 

LINKCHECK -------------------------------------| 

| | 

|-- ALL ------| 

| | 

|-- LINKS ----| 

| | 

|-- LISTS ----| 

| | 


6875 9497–003 111


LINKCHECK POOLS 

| | 

|-- POOLS ----| 

| | 

|-- WSLRU ----| 

When the POOL option is specified, the LINKCHECK command 

validates the various pool area lists within each memory 

pool structure. 

Add new sections for the MEMPOOL and POOL commands: 

o MEMPOOL (Analyze Memory Pool) 

MEMPOOL provides analysis of Memory Pool Structure Blocks. The 

command is not valid if memory pools were not in use at the time 

of the dump. 

Syntax 

MEMPOOL ----------------------------------------------------------| 

| | | | 

|--------- ---| |--- SUMMARY ---------| 

| | | | | 

|-- AT --| | |--- USAGE -----------| 

| | | | 

|-- VIA -- --------| |--- --| 

| | 

|-- IOCB ----------------------| 

| | 

|-- IOCD ----------------------| 

| | 

|-- SAVE ----------------------| 

| | | | 

|-- OLAY -| |- -| 

| | 

|-- MGR -----------------------| 

-- ----- 

|-- [] ---| 

| | 

|-- --| 

-- -- 

|-- CONTENTS ---| 

| | 

112 6875 9497–003

|-- LINKS ------| 

| | 

|-- SCANINUSE --| 

| | 

|-- LINKCHECK --| 

| | 

|-- POOLAREAS --| 

Explanation 

MEMPOOL MEMPOOL AT 


Analyze the memory pool structure block at the specified simple 

address. 

MEMPOOL VIA 

Analyze the memory pool structure block referenced by the 

specified ASD number. 

MEMPOOL IOCB 

Analyze the memory pool structure block for IOCB (I/O Control 

Block) structures. 

MEMPOOL IOCD 

Analyze the memory pool structure block for IOCD (Direct I/O 

Control Block) structures. 

MEMPOOL SAVE 

Analyze all of the memory pool structure blocks used for save 

memory allocation. 

MEMPOOL OLAY 

Analyze all of the memory pool structure blocks used for 

overlayable memory allocation. 

MEMPOOL MGR 

Analyze the contents of the global pool manager structure block. 

MEMPOOL SUMMARY 

The SUMMARY and USAGE report options produce tabular reports for 

6875 9497–003 113


the selected MEMPOOL or MEMPOOLS. For the MGR selection either 

of these options result in the POOLMGR summary report. 

MEMPOOL USAGE 




MEMPOOL SAVE [] MEMPOOL OLAY [] 

The "[]" option results in analysis of the memory pool 

structure block at the specified index. 

MEMPOOL SAVE MEMPOOL OLAY 

The option results in analysis of the memory pool 

structure block used to manage objects of the specified object size. 

MEMPOOL CONTENTS 

Analyzes the contents of every pool area associated with the 

specified memory pool structure. 

MEMPOOL LINKS 

Analyzes the object links within each pool area associated with 

the specified memory pool structure. 

MEMPOOL SCANINUSE 

Provides a summary of inuse memory areas allocated within each 

pool area associated with the specified memory pool structure. 

MEMPOOL LINKCHECK 

Reports on bad links within any of the pool areas associated with 


MEMPOOL POOLAREAS 

Analyzes all memory pool areas associated with the specified 

memory pool structure. 

114 6875 9497–003

o POOL (Analyze Pool Area) 


Analyzes the memory pool area from specified ASD or Address. 

The SPACEUSAGE of the area is checked to verify that it is 

of type POOLAREA. The command is not valid if MEMPOOLS were 

not in use at the time of the dump. 

Syntax 

POOL ----------- -----------------------| 

| | | | | 

|-- AT --| | |-- CONTENTS ---| 

| | | | 

|-- VIA -- -------| |-- LINKS ------| 

| | 


| | 


Explanation 

POOL 

POOL AT 

Analyzes the pool area beginning at the specified simple 

address. 

POOL VIA 

Analyzes the pool area referenced by the specified ASD number. 

POOL CONTENTS 

POOL AT CONTENTS 

POOL VIA CONTENTS 

Analyzes the links and contents of each object in the pool 

area in addition to the pool summary. 

POOL LINKS 

POOL AT LINKS 

POOL VIA LINKS 

Analyzes the object links within the pool area. 

POOL SCANINUSE 

POOL AT SCANINUSE 

POOL VIA SCANINUSE 

Prints a summary of inuse objects after verifying all object 

links. 

6875 9497–003 115


POOL LINKCHECK 

POOL AT LINKCHECK 

POOL VIA LINKCHECK 

Reports on bad links within the pool area. 


New Commands And Options For Memory Pool Diagnostics 



(8600 0460-512): 



Update the following sections: 

o ASDNUMBER (Actual Segment Descriptor Number) 


INPUT: ASDNUMBER 6E949 FOR 2 

ASD1[006E949]:[00001BA524] 8 660026 D259E8 

ASD1_SEGTYPEF = 1 (E-MODE OR BYTE MEMORY) 

ASD1_PRESENTTOPROCF = 1 

ASD1_CODESEGMENTHALTF = 0 

ASD1_NOTSTACKF = 1 

ASD1_ADDRESSVALIDF = 1 

ASD1_READONLYF = 0 

ASD1_ADDRESSF = 0026D259E8 

ASD2[006E949]:[00001BA525] 8 000000 00003C 






ASD2_LENGTHF = 0003C (60) 

ASD3[006E949]:[00001BA526] D 900052 1019AF 

INDEX = 00521 (1313) 

ASDINDEX = 000CD7C 

ASD4[006E949]:[00001BA527] 0 000000 A00250 


116 6875 9497–003


ASD4_OLAYSTATEF = 5 (PRESENT OVERLAYABLE SEG) 


POOL LINKA WORD = 3 006E94 901190, OFFSET = 4496 

POOL LINKB WORD = 3 000000 00003E, COREADJ = 62 

POOLAREA ASD = 006568A 






TBIT_RCWS[006E949]: 0 055D4F 931532 

DIAG STKNR = 0055D 

DIAG SDI:PWI:PSI = 1532:0F93:2 (04298216/37891080) GET 

ASD LOCK STACK = 0055D 

ASD1[006E94A]:[00001BA528] B 000000 0670E2 

NEXT AVAILABLE ASD = 00670E2 

ASD2[006E94A]:[00001BA529] B 000000 000005 






ASD2_LENGTHF = 00005 (5) 

ASD3[006E94A]:[00001BA52A] B 006804 431026 

DEALLOCATED @ 1026:0443:0 (24524860/24534200/24584050) BLOCKEXIT 

ASD4[006E94A]:[00001BA52B] B 000000 800D11 


ASD4_OLAYSTATEF = 4 (UNINIT OVERLAYABLE SEG) 







TBIT_RCWS[006E94A]: 0 1F9C4F 931532 

DIAG STKNR = 01F9C 

DIAG SDI:PWI:PSI = 1532:0F93:2 (04298216/37891080) 

GETHEADER 

ASD LOCK STACK = 01F9C 


The following shows the output from the ASD USAGE command. 

INPUT: ASD USAGE 

6875 9497–003 117


ASD 0000001 thru 006F54E Usage Summary 

-------------------------------------- 

Addr Valid Kwords PoolObj Kwords 

--------------------------------------------- ... 

NORMALAREA 266,116 47,673 255,221 21,681 

FIBMARK 1,417 153 1,417 153 

SEGDOPE 617 25 613 6 

SEGSEG 1,321 9,978 20 3 

TABMARK 960 161 950 159 

DOPEVECT 9,140 1,729 8,018 306 

IOCBAREA 2,245 132 1,197 71 

DIRECTIOBUFF 3,044 9,587 1,543 513 

EVENTAR 618 252 585 54 

DIRECTIOBUFFTOBE 0 0 0 0 

STACKMARK 839 2,027 194 67 

POOLAREA 4,049 1,046 0 0 

SIBMARK 19 2 0 0 

PIBMARK 868 203 858 200 

BUFFERHEADER 534 6 534 6 

STRUCTUREDAREA 9,289 1,297 9,165 1,289 

SUBSPACE_ARRAY 6,158 12,168 0 0 

MESSAGEAREA 2,524 82 2,520 82 

IOCDAREA 3,041 283 3,041 283 

CODEAREA 15,968 6,271 14,550 2,463 

INSTACKAREA 227 3 0 0 

ICMMARK 111 3 111 3 

IOBUFFER 482 1,021 0 0 

EVENTCONTAINERAR 692 69 681 58 

DOPEOREVENTAREA 1,453 60 359 15 

EVENTSEG 10 80 0 0 

RESERVEAREA 16 9 0 0 

EVENTMESSAGEAREA 18 1 5 1 

IOCBMESSAGEAREA 310 19 279 17 

MCBAREA 3,294 490 0 0 

EVSTATEAREA 25,814 328 25,610 326 

--------------------------------------------- ... 

Totals 365,125 97,826 329,722 28,381 

Present 

Save segments 119,424 48,153 90,418 7,389 

Overlayable 245,701 49,674 239,304 20,992 

------------------------------------------- 

365,125 97,826 329,722 28,381 

No Memory 

Uninit overlay 641 371 567 121 

OS=0/Virgin 52,795 8,301 213 104 

------------------------------------------- 

53,436 8,671 780 224 

AvailabLe ASDs 

Deallocated 5,292 

Reserved 32,161 

----------- 

37,453 

118 6875 9497–003

ASDs Examined 456,014 of 2,742,026 ( 16.63 %) 

PoolObject ASDs 329,722 of 365,125 ( 90.30 %) 

PoolObject KW 28,381 of 97,826 ( 29.01 %) 

Area Reduction 35,403 vs 361,076 ( 90.20 %) 

PoolObject/Area 81.43 in 4,049 PoolAreas 


(Please append the following to the right side of the report) 

No Mem Kwords 

... ------------------- 

13,065 2,848 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

239 299 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

10,361 34 

0 0 

29,771 5,491 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

0 0 

... ------------------- 

53,436 8,671 

6875 9497–003 119


o CU (Core Utilization) 

Replace the railroad diagram for the CU command with the 

following: 

CU---------------------------------------------------| 

| | | | 

|-- POOLS --| |-- AVAIL ------------------| 

| | 

|-- LISTS ------| 

| | 

|-- OLAYLISTS --| 

| | 

|-- SAVELISTS --| 

| | 

|-- POOLS ------| 

o LINKCHECK (Check Memory Link) 

Add the POOLS option to the LINKCHECK railroad diagram 

and add the description of the POOLS option listed below: 

|-------------------| 

V | 

LINKCHECK -------------------------------------| 

| | 

|-- ALL ------| 

| | 

|-- LINKS ----| 

| | 

|-- LISTS ----| 

| | 


| | 

|-- POOLS ----| 

| | 

|-- WSLRU ----| 

LINKCHECK POOLS 

When the POOL option is specified, the LINKCHECK command 

validates the various pool area lists within each memory 

pool structure. 

120 6875 9497–003

Add new sections for the MEMPOOL and POOL commands: 

o MEMPOOL (Analyze Memory Pool) 


MEMPOOL provides analysis of Memory Pool Structure Blocks. The 

command is not valid if memory pools were not in use at the time 

of the dump. 

Syntax 

MEMPOOL ----------------------------------------------------------| 

| | | | 

|--------- ---| |--- SUMMARY ---------| 

| | | | | 

|-- AT --| | |--- USAGE -----------| 

| | | | 

|-- VIA -- --------| |--- --| 

| | 

|-- IOCB ----------------------| 

| | 

|-- IOCD ----------------------| 

| | 

|-- SAVE ----------------------| 

| | | | 

|-- OLAY -| |- -| 

| | 

|-- MGR -----------------------| 

-- ----- 

|-- [] ---| 

| | 

|-- --| 

-- -- 

|-- CONTENTS ---| 

| | 

|-- LINKS ------| 

| | 


| | 


| | 

|-- POOLAREAS --| 

6875 9497–003 121


Explanation 

MEMPOOL MEMPOOL AT 

Analyze the memory pool structure block at the specified simple 

address. 

MEMPOOL VIA 

Analyze the memory pool structure block referenced by the 

specified ASD number. 

MEMPOOL IOCB 

Analyze the memory pool structure block for IOCB (I/O Control 

Block) structures. 

MEMPOOL IOCD 

Analyze the memory pool structure block for IOCD (Direct I/O 

Control Block) structures. 

MEMPOOL SAVE 

Analyze all of the memory pool structure blocks used for save 

memory allocation. 

MEMPOOL OLAY 

Analyze all of the memory pool structure blocks used for 

overlayable memory allocation. 

MEMPOOL MGR 

Analyze the contents of the global pool manager structure block. 

MEMPOOL SUMMARY 




MEMPOOL USAGE 




122 6875 9497–003

MEMPOOL SAVE [] MEMPOOL OLAY [] 


The "[]" option results in analysis of the memory pool 

structure block at the specified index. 

MEMPOOL SAVE MEMPOOL OLAY 

The option results in analysis of the memory pool 

structure block used to manage objects of the specified object size. 

MEMPOOL CONTENTS 

Analyzes the contents of every pool area associated with the 

specified memory pool structure. 

MEMPOOL LINKS 

Analyzes the object links within each pool area associated with 


MEMPOOL SCANINUSE 

Provides a summary of inuse memory areas allocated within each 

pool area associated with the specified memory pool structure. 

MEMPOOL LINKCHECK 

Reports on bad links within any of the pool areas associated with 


MEMPOOL POOLAREAS 

Analyzes all memory pool areas associated with the specified 

memory pool structure. 

o POOL (Analyze Pool Area) 

Analyzes the memory pool area from specified ASD or Address. 

The SPACEUSAGE of the area is checked to verify that it is 

of type POOLAREA. The command is not valid if MEMPOOLS were 

not in use at the time of the dump. 

6875 9497–003 123


Syntax 

POOL ----------- -----------------------| 

| | | | | 

|-- AT --| | |-- CONTENTS ---| 

| | | | 

|-- VIA -- -------| |-- LINKS ------| 

| | 


| | 


Explanation 

POOL 

POOL AT 

Analyzes the pool area beginning at the specified simple 

address. 

POOL VIA 

Analyzes the pool area referenced by the specified ASD number. 

POOL CONTENTS 

POOL AT CONTENTS 

POOL VIA CONTENTS 

Analyzes the links and contents of each object in the pool 

area in addition to the pool summary. 

POOL LINKS 

POOL AT LINKS 

POOL VIA LINKS 

Analyzes the object links within the pool area. 

POOL SCANINUSE 

POOL AT SCANINUSE 

POOL VIA SCANINUSE 

Prints a summary of inuse objects after verifying all object 

links. 

POOL LINKCHECK 

POOL AT LINKCHECK 

POOL VIA LINKCHECK 

Reports on bad links within the pool area. 

124 6875 9497–003


FIB Command Now Supports An ALL Stacks Option 



The syntax of the FIB command is extended to accept a value of 

ALL when using the STACK option. 





FIB (File Information Block) 

Add the ALL option to the SYNTAX diagram as follows: 

FIB----------------- -------| 

| | | 

|-- AT --| | 

| | 

|-- VIA -- ---------| 

| | 

|-- STACK --- ----| 

| | | | 

| |----- ALL --------| | 

| | 

|-- ---------| 

| | 

|-- ----| 

In the explanation section add the following: 

FIB STACK ALL 

Analyzes the FIB for every file opened by all stacks. 

6875 9497–003 125


EDITOR 

Component: MACROS PRI-11517811 

Add New Macros For Dumpanalyzer Commands 


The following editor macros have been added to the 

SHARED/EDITOR/MACROS/DUMP file: 

LISts Analyze list structures. 

LOGRecord Display log records in memory. 

MCB Analyze MCB structure. 

MEMPool Display memory pool structure information. 

MEMRQ Analyze memory result queue. 

POOl Analyze a memory pool area. 

QTrace Display datacom queue trace. 

RCB Analyze RCB structure. 

RCWtoseq Convert RCW into sequence number. 

RESIZETRace Display resize trace information. 

SHAREDBuff Display shared buffers for a file. 

SSAQ Analyze the StoreSafe alert queue. 

USERCommand Execute a command in a user library. 

USERLib Load a user library. 

Component: MACROS PRI-11537731 

Add New Macros For Dumpanalyzer Commands 


The following editor macros have been added to the 

SHARED/EDITOR/MACROS/DUMP file: 

LISts Analyze list structures. 

LOGRecord Display log records in memory. 

126 6875 9497–003

EMAIL 

MCB Analyze MCB structure. 


MEMPool Display memory pool structure information. 

MEMRQ Analyze memory result queue. 

POOl Analyze a memory pool area. 

QTrace Display datacom queue trace. 

RCB Analyze RCB structure. 

RCWtoseq Convert RCW into sequence number. 

RESIZETRace Display resize trace information. 

SHAREDBuff Display shared buffers for a file. 

SSAQ Analyze the StoreSafe alert queue. 

USERCommand Execute a command in a user library. 

USERLib Load a user library. 

Component: EMAIL PRI-11483704 

Clarify Server Specification in *INSTALLATION/OPTIONS File 


Section 9 (EMAIL Utility) of the System Software Utilities 

Operations 

Reference Manual (8600 0460), which describes how to install the 

EMAIL utility, is being clarified with regards to how a mail server 

address may be specified. 

The railroad diagram for the syntax currently specifies 

that an address can be followed by another address in parentheses. 

This is incorrect. An address can be specified with out 

parentheses when not specifiying any attributes or an address can 

be specified with parentheses when specifying attributes. Multiple 

addresses need 

to be separated with a comma. The syntax is being corrected as 

follows: 

 

6875 9497–003 127


|


Add the following new paragraph after the last paragraph: 

If you specify TOENDRESTORE it works the same as TOEND except 

if copying to the tape is terminated by an error. For an error 

case, library maintenance restores the LIBMAINTDIR disk file 

to the state it was in before the copy started. This means 

that the LIBMAINTDIR file for the tape will not contain any 

information about the files that were appended to the tape 

before the error occurred. 

Add the following to the "" railroad diagram in the 

"FILECOPY Options" sub-section of the "FILECOPY" section. 

|-- JOBNAME --- ------------------------| 

Component: FILECOPY PRI-11419305 

INCLUDE FILEKIND Produces Incorrect Results 

SYMPTOMS: 

The INCLUDE FILEKIND option produces unpredictable results. Unlike 

the EXCLUDE FILEKIND option, it ignores the selection criteria. It 

only affects a single family rather than all files selected by the 

task. 


Add the following information about the INCLUDE FILEKIND option to 

the FILECOPY section of the System Software Utilities Operations 

Reference Manual (form # 8600 0460-511). 

Add INCLUDE FILEKIND to the railroad diagram : 

++ 

+ + 

--------INCLUDE FILEKIND (--+---< filekind >---+--)------------ 

Add the following explanation of INCLUDE FILEKIND () 

option to the FILECOPY Options table: 

Causes files to be copied based on their FILEKIND values 

(ALGOLCODE, DATA, and so forth). If an INCLUDE FILEKIND option 

is specified, only files of the specified filekinds will be 

included, unless the file is explicitly included by name. 

INCLUDE FILEKIND and EXCLUDE FILEKIND are mutually exclusive. 

Add the following to the explanation of the EXCLUDE FILEKIND 

() options in the FILECOPY Options table: 

INCLUDE FILEKIND and EXCLUDE FILEKIND are mutually exclusive. 

6875 9497–003 129


Add an additional example to the Sample FILECOPY Runs topic: 

The following example demonstrates the use of the INCLUDE 

FILEKIND option. It copies all COBOL74SYMBOL and COBOL85SYMBOL 

files from the specified directories to tape. 

ALLFILES 

FILES ((UC1)SYMBOL/= FROM USER1, 

(UC2)SYMBOL/= FROM USER1) 

TO COBOLSYMBOLS (TAPE) 

INCLUDE FILEKIND (COBOL74SYMBOL) 

INCLUDE FILEKIND (COBOL85SYMBOL) 

NOZIP LOCKDECK DECKLABEL JOB/FILECOPY/COBOLFILES 


Exclusion Of Files Which Are In-Use 

SYMPTOMS: 

FILECOPY will select all files on selection criteria regardless of 

whether the file is in-use or not. 


An ACCESSED task request may select a file that is in-use because 

the last access date has not been updated. Now FILECOPY can exclude 

files that are in-use by specifying the SKIPINUSE option. 

Add the following information about the SKIPINUSE option to the 

FILECOPY Options section of the System Software Utilities 

Operations Reference Manual (form # 8600 0460). 

Add SKIPINUSE to the railroad diagram (Page : 10-21) : 

|-------SKIPINUSE ------------------------------------------| 

Note: SKIPI should be in bold. 

Add the following explanation of the SKIPINUSE option to the 

FILECOPY Options table (Table 10-6): 

Omits in-use files from file selection criteria. SKIPINUSE applies 

only to files selected by the FILES modifier. The INCLUDE modifier 

overrides the SKIPINUSE option. That is, if a file is included 

because it is named in an INCLUDE modifier, then the file will be 

copied whether or not it is in-use. 

130 6875 9497–003


DENSITY Description Contains Extraneous Text 


SYMPTOMS: 

Description of the DENSITY modifier in System Software Utilities 

Operations Reference Manual contains extraneous text. 


In Table 10-5 of the System Software Utilities Operations Reference 

Manual (8600-0460) for the DENSITY modifier delete the second 

sentence i.e., "The unit number can be used only if the OLDWFL 

option is specified.". 


DENSITY Description Contains Extraneous Text 

SYMPTOMS: 

Description of the DENSITY modifier in System Software Utilities 

Operations Reference Manual contains extraneous text. 


In Table 10-5 of the System Software Utilities Operations Reference 

Manual (8600-0460) for the DENSITY modifier delete the second 

sentence i.e., "The unit number can be used only if the OLDWFL 

option is specified.". 

FILEDATA 

Component: FILEDATA PRI-11428967 

DECK Modifier in COPYDECK Request 

SYMPTOMS: 

The COPYDECK FILEDATA request generates a file with a filekind of 

DATA. 


The DECK modifier can now be used in a COPYDECK request. This will 

generate an output file of filekind JOBSYMBOL. 

Add the following description to the System Software Utilities 

Operations Reference Manual (form # 8600 0460). All changes are 

to the "FILEDATA Utility" section. 

6875 9497–003 131


In the "COPYDECK Request" topic of the "Task Requests" topic: 

o Add the following to the first paragraph: 

You can use the DECK modifier to create a disk file with 

FILEKIND = JOBSYMBOL. 

o Add DECK = to the syntax diagram for 

 

o Add DECK to the list of FILEDATA modifiers. 

In the "FILEDATA Modifiers" topic of the "FILEDATA Utility" 

section, add: 

DECK 

The DECK = modifier causes the output to be 

written to a disk file. The title of the output file is 

the supplied file title. The following attributes are 

set, overriding any attributes specified in a DEFINEOUTPUT 

request. 

FILEKIND JOBSYMBOL 

MAXRECSIZE 90 

The DECK modifier is only valid with a COPYDECK request. 


Database Level Information 

SYMPTOMS: 

Reuse of FILEDATA databases when the FILEDATA database version 

changes is not well documented. 


The message generated when an incompatible database is specified 

now includes the database version levels. 

For example, the following message may be generated: 

DATABASE AND FILEDATA LEVELS (48100, 52100) ARE NOT COMPATIBLE. 

Database versions are normally only changed when the FILEDATA 

release changes. However, a change introduced in FILEDATA-052.1A.6 

necessitated a change in the database version. A database 

generated by FILEDATA prior to this IC level cannot be used with 

the 052.1A.6 or later version of FILEDATA. 

Add the following to the FILEDATA Utility section of the System 

132 6875 9497–003


Software Utilities Operations Reference Manual (form # 8600 0460). 

Add a new sub-topic to the Database Generation and Reuse topic. 

Database Version Levels 

A version level is stored in the database generated by FILEDATA. 

When the format of the database changes so that a version of 

FILEDATA different from the creating FILEDATA cannot use the 

database, the version level is incremented. 

If a saved database (created with the NEWDATABASE modifier) is 

reused (by using the DATABASE modifier), the database version 

level must be compatible with the FILEDATA version. 


Using CANDE U to Run FILEDATA Gets an Error Report 

SYMPTOMS: 

U *SYSTEM/FILEDATA ATTR: DIR=SYMBOL 

Gets the error report: 

NUMERIC REPORT INPUT = 

where varies. 


Make the following change to the "System Software Utilities 

Operations Reference Manual". In the "FILEDATA Utility" section, 

under "Numeric Report Requests", delete the two references to 

5: 

Change "... 0, 1, 3, and 5 ..." to 

Reports for 0, 1, and 3 are currently defined. 

Delete the sentence: 

A number 5 is equivalent to the COMPILEDECK task request. 

6875 9497–003 133



FILEDATA Reports PROTECTED File Attribute 


FILEDATA will report the PROTECTION = PROTECTED file attribute 

value for LFILES requests and ATTRIBUTES requests. 

For the LFILES and ATTRIBUTES cases, if you specify ALL or 

PROTECTION then FILEDATA will report the value of the PROTECTION 

attribute as PROTECTED or SAVE. 



FTP 













Component: FTPSUPPORT PRI-11541348 

Allow Directory COPY and Multi-File Command 

SYMPTOMS: 

FTP does not allow a directory to be used in a COPY command. 

The command "COPY [FTP] FOLDER1/= FROM ...." returns a syntax 

error and the copy is aborted. 

134 6875 9497–003


The FTP Interactive Client does not support the MGET and MPUT 

commands. The command "MGET TEST=" returns an unknown command 

error. 


FTP now supports multi-file transfers. The Batch Client and 

Interactive Client have been updated to allow a user to 

specify a wildcard in the file name being transferred. The 

wildcard creates a list of file names that match the syntax 

of the string entered and the list of files are included in 

the file transfer. 

The following changes should be made to the TCP/IP Distributed 

Systems Services Operations Guide (8807 6385-014). 

The following text should be changed on page 5-21 under 

'Restrictions on FTP'. 

The bullet "Do not send a directory" should be removed. 

The following should be added to page 5-8 under 

'Example of Copying to or from a Remote Host'. 

All files under a directory can be copied between the local 

and remote host. When specifying a directory on a remote 

host, each node in the directory must exist before the 

COPY command is entered. If the remote directory in the 

COPY command is XX/YY/ZZ/= - the folders XX, YY, and 

ZZ must exist on the remote host. 

When a directory copy is performed and a file within the 

directory has a nonstandard MCP filename, the filename 

is converted following the rules used by the 

NONNATIVE_FILENAMES option. This conversion takes place 

regardless of the setting of this option. For more 

information on how nonstandard names are converted on the 

MCP, see Section 8 under the NONNATIVE_FILENAMES Option. 

Under the 'Local to Remote' topic. 

Transfer a directory to IP Address 

The following example transfers all files in the TEST/FILE 

directory including files under any sub-directories to the 

remote server. 

COPY [FTP] TEST/FILE/= FROM DISK(PACK) 

TO DISK(IPADDRESS = "10.1.0.52", 

USERCODE = MR1/IAX/500421) 

6875 9497–003 135


Under the 'Remote to Local' topic. 

Transfer a directory from a Hostname 

The following example transfers all files in the 

ACCT/BILLING folder including all files under any 

sub-folders and places them in the 

SALES/ACCT/BILLING directory on the local host. 

COPY [FTP] ACCT/BILLING/= AS SALES/ACCT/BILLING/= 

FROM DISK(HOSTNAME = SALES, 

USERCODE = MRKT/JAMES/532014) 

TO DISK(PACK) 

The following text should be added to page 6-2 under 

'Interactive FTP Client Commands, by Functional Group'. 

Add the following group after the 'Directory and File Commands' 

grouping. 

Multiple File Commands 

Use the multi-file commands to transfer and delete 

files. 

MDELETE - Deletes files that match the search 

criteria in the command options. 

MGET - Retrieves files from the remote server 

that match the search criteria in the command 

options. 

MPUT - Sends files to the remote system that 

match the search criteria in the command 

options. 

Add the following commands under 'Interactive FTP Client 

Commands, by Name' on page 6-13. 

MDELETE - Deleting Multiple Files 

Use the MDELETE command to request the remote FTP 

server to remove all files that match the search 

critera. 

136 6875 9497–003

Syntax 


MDELETE ---------------------------------------------| 

| | 

| |---- < -- ---------| | 

|---- ----| 

Explanation 

The specifies the matching 

criteria used to select the files to be deleted. 

The equal sign (=) can be used as a wildcard in 

the string to mask the search string used to select 

the files to be included. 

Prompting 

If you do not supply a file selection criteria, the 

client prompts you for it. 

Examples 

dir testfolder/* 

@ 200 Command okay. 

@ 150 Opening ASCII mode data connection for file list. 

@ drwxrw-rw- 1 user group 

0 Jun 4 14:49 Empy Folder 


0 Jun 15 13:24 MCP Rtrn 

@ -rw-rw-rw- 1 user group 

2627 Feb 4 11:57 test 


1046 Feb 2 13:51 test.txt 


0 Jun 10 15:51 TestFolder 2 


1046 Feb 2 13:51 text2abc.txt 


23040 May 29 16:01 text4a 


12384 May 29 15:59 text4a.txt 

@ 226 Transfer complete. 527 bytes transferred. 527 Bps. 

@ The DIR Request was successfully processed by host 

"192.123.248.4" 

mdelete testfolder/tex= 







@ Enter 'Cancel' to terminate the MDELETE command. 

@ MDELETE: Delete file testfolder/text2abc.txt? 

6875 9497–003 137


(Yes/No/Cancel). 

n 

@ MDELETE: Delete file testfolder/text4a? 


y 

@ 250 DELE command successful. 

@ The MDELETE Request was successfully processed by host 

"192.123.248.4" 

@ MDELETE: Delete file testfolder/text4a.txt? 


n 

@ 

MGET - Transferring Multiple Files from Remote 

to Local Systems 

Use the MGET command to retrieve multiple files 

from the remote server and store them on your 

local system. 

Syntax 

MGET -------------------------------------------------| 

| | 

| |---- < -- ---------| | 

|---- ----| 

Explanation 


criteria used to select the files to be retrieved. 




Prompting 



Examples 









2627 Feb 4 11:57 test 

138 6875 9497–003



1046 Feb 2 13:51 test.txt 






23040 May 29 16:01 text4a 


12384 May 29 15:59 text4a.txt 



"192.123.248.4" 

mget testfolder/=.txt 







@ Enter 'Cancel' to terminate the MGET command. 

@ MGET: Transfer file testfolder/test.txt? 


n 

@ MGET: Transfer file testfolder/text2abc.txt? 


n 

@ MGET: Transfer file testfolder/text4a.txt? 


y 


@ 150 Opening ASCII mode data connection 

for testfolder/text4a.txt. 

@ 226 Transfer complete. 12384 bytes 

transferred. 12384 Bps. 

@ TESTFOLDER/"TEXT4A.TXT" transferred successfully 

@ 12384 octets transferred in 0 seconds 

(290802.5 / second) 

MPUT - Transferring Multiple Files from Local 

to Remote Systems 

Use the MPUT command to send multiple files to the 


Syntax 

MPUT -------------------------------------------------| 

| | 

| |---- < -- ---------| | 

|---- ----| 

6875 9497–003 139


Explanation 


criteria used to select the files to be stored. 




Prompting 



Examples 

LOCAL MCP FILES 

=============== 

TESTFOLDER/BC/"SSL_FDS.TXT" 

TESTFOLDER/BC/"BATCH_COPY.TXT" 

TESTFOLDER/BC/"BATCH_MGET.TXT" 

TESTFOLDER/"MCP RTRN"/"TEST1.TXT" 

TESTFOLDER/"TEXT4A.TXT" 

TESTFOLDER/BATCH_COPY 

mput testfolder/bc/= 

@ Enter 'Cancel' to terminate the MPUT command. 

@ MPUT: Transfer file TESTFOLDER/BC/"SSL_FDS.TXT"? 


n 

@ MPUT: Transfer file TESTFOLDER/BC/"BATCH_COPY.TXT"? 


n 

@ MPUT: Transfer file TESTFOLDER/BC/"BATCH_MGET.TXT"? 


y 


@ 150 Opening ASCII mode data connection for 

TESTFOLDER/BC/BATCH_MGET.TXT. 



@ TESTFOLDER/BC/"BATCH_MGET.TXT" transferred successfully 

@ 182442 octets transferred in 0.2 seconds 

(1206531.2 / second) 

PROMPT - User Confirmation for Multiple Files Action 

Use the PROMPT command to set or reset the PROMPT 

option. When set, the user is requested to confirm 

the filename to be used in a multiple file request. 

The initial setting is set by the OPTION command. 

140 6875 9497–003

Syntax 


--- PROMPT ------------------------------------| 

|--- + ---| 

|--- - ---| 

Examples 

PROMPT - 

Results 

The PROMPT command can be used to set or reset the 

option to verify the action being taken for each 

file in a multiple file request. 

If the PROMPT option is set each file name is displayed 

and a specific action is requested. 

@ MPUT: Transfer file FOLDER1/FILEA? (Yes/No/Cancel). 

The following responses to the command can be entered. 

Yes - the action on the file is taken and when 

completed the next file is displayed. 

No - the action on the file is not taken and 

the next file is displayed. 

Cancel - the action on the file is not taken and 

the multiple file command is canceled. 

The following changes should be made to the OPTIONS command 

on page 6-44. 

Under the Syntax heading add the PROMPT option after 

the DEBUG option and before the SCAN_LOGIN_INFO option. 

|--- DEBug -----------------| 

|--- PROMPT ----------------| 

|--- SCAn_loging_info ------| 

Under the Explanation heading ad the PROMPT option 

description below. 

PROMPT 

The PROMPT option is used to confirm each file name 

6875 9497–003 141


to be included in a list of files found for a 

multiple file command. When a MDELETE, MGET, or MPUT 

command is entered, each file that matches the search 

string will be displayed. 

Component: FTPSUPPORT PRI-11541356 

Allow Directory COPY and Multi-File Command 

SYMPTOMS: 

FTP does not allow a directory to be used in a COPY command. 

The command "COPY [FTP] FOLDER1/= FROM ...." returns a syntax 

error and the copy is aborted. 

The FTP Interactive Client does not support the MGET and MPUT 

commands. The command "MGET TEST=" returns an unknown command 

error. 


FTP now supports multi-file transfers. The Batch Client and 

Interactive Client have been updated to allow a user to 

specify a wildcard in the file name being transferred. The 

wildcard creates a list of file names that match the syntax 

of the string entered and the list of files are included in 

the file transfer. 

The following changes should be made to the TCP/IP Distributed 

Systems Services Operations Guide (8807 6385-014). 

The following text should be changed on page 5-21 under 

'Restrictions on FTP'. 

The bullet "Do not send a directory" should be removed. 

The following should be added to page 5-8 under 

'Example of Copying to or from a Remote Host'. 

All files under a directory can be copied between the local 

and remote host. When specifying a directory on a remote 

host, each node in the directory must exist before the 

COPY command is entered. If the remote directory in the 

COPY command is XX/YY/ZZ/= - the folders XX, YY, and 

ZZ must exist on the remote host. 

When a directory copy is performed and a file within the 

142 6875 9497–003


directory has a nonstandard MCP filename, the filename 

is converted following the rules used by the 

NONNATIVE_FILENAMES option. This conversion takes place 

regardless of the setting of this option. For more 

information on how nonstandard names are converted on the 

MCP, see Section 8 under the NONNATIVE_FILENAMES Option. 

Under the 'Local to Remote' topic. 

Transfer a directory to IP Address 

The following example transfers all files in the TEST/FILE 

directory including files under any sub-directories to the 


COPY [FTP] TEST/FILE/= FROM DISK(PACK) 

TO DISK(IPADDRESS = "10.1.0.52", 

USERCODE = MR1/IAX/500421) 

Under the 'Remote to Local' topic. 

Transfer a directory from a Hostname 

The following example transfers all files in the 

ACCT/BILLING folder including all files under any 

sub-folders and places them in the 

SALES/ACCT/BILLING directory on the local host. 

COPY [FTP] ACCT/BILLING/= AS SALES/ACCT/BILLING/= 

FROM DISK(HOSTNAME = SALES, 

USERCODE = MRKT/JAMES/532014) 

TO DISK(PACK) 

The following text should be added to page 6-2 under 

'Interactive FTP Client Commands, by Functional Group'. 

Add the following group after the 'Directory and File Commands' 

grouping. 

Multiple File Commands 

Use the multi-file commands to transfer and delete 

files. 

MDELETE - Deletes files that match the search 

criteria in the command options. 

6875 9497–003 143


MGET - Retrieves files from the remote server 

that match the search criteria in the command 

options. 

MPUT - Sends files to the remote system that 

match the search criteria in the command 

options. 

Add the following commands under 'Interactive FTP Client 

Commands, by Name' on page 6-13. 

MDELETE - Deleting Multiple Files 

Use the MDELETE command to request the remote FTP 

server to remove all files that match the search 

critera. 

Syntax 

MDELETE ---------------------------------------------| 

| | 

| |---- < -- ---------| | 

|---- ----| 

Explanation 


criteria used to select the files to be deleted. 




Prompting 



Examples 









2627 Feb 4 11:57 test 


1046 Feb 2 13:51 test.txt 

144 6875 9497–003







23040 May 29 16:01 text4a 


12384 May 29 15:59 text4a.txt 



"192.123.248.4" 

mdelete testfolder/tex= 







@ Enter 'Cancel' to terminate the MDELETE command. 

@ MDELETE: Delete file testfolder/text2abc.txt? 


n 

@ MDELETE: Delete file testfolder/text4a? 


y 

@ 250 DELE command successful. 

@ The MDELETE Request was successfully processed by host 

"192.123.248.4" 

@ MDELETE: Delete file testfolder/text4a.txt? 


n 

@ 

MGET - Transferring Multiple Files from Remote 

to Local Systems 

Use the MGET command to retrieve multiple files 

from the remote server and store them on your 

local system. 

Syntax 

MGET -------------------------------------------------| 

| | 

| |---- < -- ---------| | 

|---- ----| 

Explanation 


criteria used to select the files to be retrieved. 

6875 9497–003 145





Prompting 



Examples 









2627 Feb 4 11:57 test 


1046 Feb 2 13:51 test.txt 






23040 May 29 16:01 text4a 


12384 May 29 15:59 text4a.txt 



"192.123.248.4" 

mget testfolder/=.txt 







@ Enter 'Cancel' to terminate the MGET command. 

@ MGET: Transfer file testfolder/test.txt? 


n 

@ MGET: Transfer file testfolder/text2abc.txt? 


n 

@ MGET: Transfer file testfolder/text4a.txt? 


y 


@ 150 Opening ASCII mode data connection 

for testfolder/text4a.txt. 

146 6875 9497–003




@ TESTFOLDER/"TEXT4A.TXT" transferred successfully 

@ 12384 octets transferred in 0 seconds 

(290802.5 / second) 

MPUT - Transferring Multiple Files from Local 

to Remote Systems 

Use the MPUT command to send multiple files to the 


Syntax 

MPUT -------------------------------------------------| 

| | 

| |---- < -- ---------| | 

|---- ----| 

Explanation 


criteria used to select the files to be stored. 




Prompting 



Examples 

LOCAL MCP FILES 

=============== 

TESTFOLDER/BC/"SSL_FDS.TXT" 

TESTFOLDER/BC/"BATCH_COPY.TXT" 

TESTFOLDER/BC/"BATCH_MGET.TXT" 

TESTFOLDER/"MCP RTRN"/"TEST1.TXT" 

TESTFOLDER/"TEXT4A.TXT" 

TESTFOLDER/BATCH_COPY 

mput testfolder/bc/= 

@ Enter 'Cancel' to terminate the MPUT command. 

@ MPUT: Transfer file TESTFOLDER/BC/"SSL_FDS.TXT"? 


n 

@ MPUT: Transfer file TESTFOLDER/BC/"BATCH_COPY.TXT"? 


6875 9497–003 147


n 

@ MPUT: Transfer file TESTFOLDER/BC/"BATCH_MGET.TXT"? 


y 


@ 150 Opening ASCII mode data connection for 

TESTFOLDER/BC/BATCH_MGET.TXT. 



@ TESTFOLDER/BC/"BATCH_MGET.TXT" transferred successfully 

@ 182442 octets transferred in 0.2 seconds 

(1206531.2 / second) 

PROMPT - User Confirmation for Multiple Files Action 

Use the PROMPT command to set or reset the PROMPT 

option. When set, the user is requested to confirm 

the filename to be used in a multiple file request. 

The initial setting is set by the OPTION command. 

Syntax 

--- PROMPT ------------------------------------| 

|--- + ---| 

|--- - ---| 

Examples 

PROMPT - 

Results 

The PROMPT command can be used to set or reset the 

option to verify the action being taken for each 

file in a multiple file request. 

If the PROMPT option is set each file name is displayed 

and a specific action is requested. 

@ MPUT: Transfer file FOLDER1/FILEA? (Yes/No/Cancel). 

The following responses to the command can be entered. 

Yes - the action on the file is taken and when 

completed the next file is displayed. 

No - the action on the file is not taken and 

the next file is displayed. 

Cancel - the action on the file is not taken and 

the multiple file command is canceled. 

148 6875 9497–003


The following changes should be made to the OPTIONS command 

on page 6-44. 

Under the Syntax heading add the PROMPT option after 

the DEBUG option and before the SCAN_LOGIN_INFO option. 

|--- DEBug -----------------| 

|--- PROMPT ----------------| 

|--- SCAn_loging_info ------| 

Under the Explanation heading ad the PROMPT option 

description below. 

PROMPT 

INFOACCESS 

The PROMPT option is used to confirm each file name 

to be included in a list of files found for a 

multiple file command. When a MDELETE, MGET, or MPUT 

command is entered, each file that matches the search 

string will be displayed. 

Component: INFOACCESS PRI-11456189 

Modify Documentation regarding support for Windows 

SYMPTOMS: 

Some documentation still refers to unsupported versions of 

Microsoft Windows. 


Make the following changes to the ODBC Access for ClearPath 

MCP Administrator User's Guide (8999 5385): 

1) Change the first bullet under System Requirements in Section 1 

from "Microsoft Windows NT 4.0 with Service Pack 4 or later 

or any edition of Windows 2000 or later is installed." to 

"Most currently supported versions of Microsoft Windows. Refer to 

the Unisys Product Support Compatibility Matrix for ClearPath MCP 

for specific versions". 

2) In the fourth bullet under System Requirements in 

Section 1 change "This is standard on Windows 2000 or later." 

6875 9497–003 149


to "This is standard on all currently supported versions of 

Windows.". 

3) Under Servers Node in Section 2, remove the sentence, 

"The ODBC Access Windows server can also be installed on a 

Windows NT 4.0 with Service Pack 4 or Windows 2000 workstation 

or later for low volume use, such as that required by a 

developer.". 

Make the following changes to the ODBC Access for ClearPath MCP 

Installation and Operations Guide (8807 9314): 

1) Under System Architecture in Section 1, replace the second and 

third bullet with the following one bullet : 

"Most currently supported versions of Microsoft Windows. Refer to 

the Unisys Product Support Compatibility Matrix for ClearPath MCP 

for specific versions. From here on, we will use the term 

ODBC Access compatible Windows operating system to refer to this.". 

Also, remove the Note under the third bullet. 

2) Under Prerequisites in Section 3, change "This is standard 

on Windows ME, and on Windows 2000 or later systems." to "This 

is standard on all currently supported versions of Windows.". 

3) Under Installing the ODBC Access SQL Server Software in 

Section 3, remove the following text: 

Ensure that your system supports Windows Installer (WI) 2.0 and 

uses Windows ME or Window s 2000 or later. If needed, you can 

access WI software from the Microsoft web site at 

http://www.microsoft.com/downloads/search.asp? 

4) Under Add a New User in Section 11, remove the sentence 

"(ODBC Access can be installed on a Windows NT 4.0 domain but 

not on a Windows NT 4.0 PC.)". 

5) Under Remove a User in Section 11, remove the sentence 

"(ODBC Access can be installed on a Windows NT 4.0 domain but 

not on a Windows NT 4.0 PC.)". 

6) Under ODBC Access SQL Server Errors in Section B, remove the 

following text: 

On a Windows ME system, the hosts and services files are 

located in the installation folder. The installation folder 

can be found by typing the following command at the command 

prompt: 

echo %windir% 

7) Replace all remaining occurrences of "Windows 2000 or later 

systems" with "ODBC Access compatible Windows operating 

systems". 

150 6875 9497–003

JDBCFORMCP-TYPE4 

Component: JDBCFORMCP-TYPE4 PRI-11392164 

JDBC Connection String Not Supporting the IPV6 

HOSTNAMENAME 


SYMPTOMS: 

The token ";;" of an IPV6 hostname 

(e.g. "FEC0::42F1:2:B3FF:FECD:23FF") is not processed by the 

DriverManager method getConnection() properly. Whenever the 

method encounters a token ":", it will interpret the token as 

another parameter or delimiter under the JDBC Connection String. 


In the section "Developing An Application Connecting to the 

Database Using the Type 4 Driver" of the online documentation 

"JDBC for ClearPath MCP User's Guide" 

At the end of the paragraph: 

Example 

con = DriverManager.getConnection(url); 

JRAC 

Append the following: 

Note:When IPv6 MCP hostname (e.g. "FEC0::42F1:2:B3FF:FECD:23FF") 

is used, a user should set a host property instead of having 

hostname in the connection string. 

private static final String url = "jdbc:unisys:dmsql: 

Unisys.DMSII:resource=STOCKEXAMPLE;port=1897;user=test; 

password=test"; 

Properties prop = new Properties(); 

prop.setproperty("host", "FEC0::42F1:2:B3FF:FECD:23FF"); 

... 

con = DriverManager.getConnection(url, prop); 

Component: JRAC PRI-11566839 

java.net.BindException - Address already in use: JVM_Bind 

SYMPTOMS: 

During initialization, JBoss receives a BindException on port 1099 

which is in use by the TIP Server resource manager. Currently, it 

is not possible to configure the TIP Server to use a different 

port number. 

6875 9497–003 151



The RMI registry and RMID port numbers can now be configured for 

the TIP Server. Configuration of these ports takes place on the 

start up scripts, startTIP.cmd and startTIP.sh. These scripts now 

take the following options: 

- rmiRegistryPort represents the RMI registry port number 

- rmidPort represents the port number of RMID's internal registry 

The options are used as follows: 

startTIP [-rmiRegistryPort ] 

[-rmidPort ] 

For example: 

startTIP -rmiRegistryPort 10990 -rmidPort 10980 

In this example, the startTIP script will first start the RMI 

registry executable, rmiregistry, on port 10990. Next, the script 

starts the RMID executable, rmid, on port 10980. 

The TIP server could use RMID's internal registry. This is 

accomplished by using the same port number for the rmiRegistryPort 

and rmidPort options. For example: 


In this example, the startTIP scripts will only start the rmid 

executable, the rmiregistry executable is not started. 

This technique works successfully with the RMI and RMID 

implementations provided with the Java SE implementation from Sun 

Microsystems, however, this technique may not be permitted with 

Java implementations from other vendors. 

The port numbers can be hard coded inside the scripts as an 

alternative to using the rmiRegistryPort and rmidPort options. 

Scripts have also been provided to stop the TIP server and RMID 

process (the RMI registry will have to be manually terminated if 

it's not using the RMID registry). The scripts are called 

stopTIP.cmd used for the Windows environment and stopTIP.sh for 

Unix and Linux environments 

The stopTIP scripts use the rmidPort option to stop a RMID 

instance that's not using the 1098 default port number for its 

internal RMI registry. For example, 

stopTIP -rmidPort 10990 

RMID can also be stopped directly by executing the following 

command: 

152 6875 9497–003

mid -stop 


Or use the following command variant if RMID was started with a 

different value for its internal RMI registry 

rmid -port -stop 

Additionally, a new configuration property has been added called 

RmiRegistryPort that enables a resource adapter instance to locate 

the TIP server. 

This property can be configured in the or the 

section of the resource adapter's 

ra.xml deployment descriptor. For example, 

 

COMSResourceAdapter 

 

 

RmiRegistryPort 

java.lang.String 

10990 

 


Use the rmiRegistryPort option to specify the port number that 

the RMI registry is started on, and rmidPort option to specify 

RMID's internal RMI registry 

2) Update the ra.xml deployment descriptor 

Add an entry for the RmiRegistryPort configuration property 

with the property's value set to the location of the RMI 

registry containing the TIP server reference. 

3) Update jbossjta-properties.xml (JBoss users) 

Use the tip.rmi.registry.port property to identify the RMI 

registry port number containing the TIP server reference. 


java.net.BindException - Address already in use: JVM_Bind 

SYMPTOMS: 

During initialization, JBoss receives a BindException on port 1099 

which is in use by the TIP Server resource manager. Currently, it 

is not possible to configure the TIP Server to use a different 

port number. 


The RMI registry and RMID port numbers can now be configured for 

the TIP Server. Configuration of these ports takes place on the 

start up scripts, startTIP.cmd and startTIP.sh. These scripts now 

take the following options: 

- rmiRegistryPort represents the RMI registry port number 

- rmidPort represents the port number of RMID's internal registry 

The options are used as follows: 

startTIP [-rmiRegistryPort ] 

[-rmidPort ] 

For example: 


In this example, the startTIP script will first start the RMI 

registry executable, rmiregistry, on port 10990. Next, the script 

starts the RMID executable, rmid, on port 10980. 

The TIP server could use RMID's internal registry. This is 

accomplished by using the same port number for the rmiRegistryPort 

and rmidPort options. For example: 

154 6875 9497–003



In this example, the startTIP scripts will only start the rmid 

executable, the rmiregistry executable is not started. 

This technique works successfully with the RMI and RMID 

implementations provided with the Java SE implementation from Sun 

Microsystems, however, this technique may not be permitted with 

Java implementations from other vendors. 

The port numbers can be hard coded inside the scripts as an 

alternative to using the rmiRegistryPort and rmidPort options. 

Scripts have also been provided to stop the TIP server and RMID 

process (the RMI registry will have to be manually terminated if 

it's not using the RMID registry). The scripts are called 

stopTIP.cmd used for the Windows environment and stopTIP.sh for 

Unix and Linux environments 

The stopTIP scripts use the rmidPort option to stop a RMID 

instance that's not using the 1098 default port number for its 

internal RMI registry. For example, 

stopTIP -rmidPort 10990 

RMID can also be stopped directly by executing the following 

command: 

rmid -stop 

Or use the following command variant if RMID was started with a 

different value for its internal RMI registry 

rmid -port -stop 

Additionally, a new configuration property has been added called 

RmiRegistryPort that enables a resource adapter instance to locate 

the TIP server. 

This property can be configured in the or the 

section of the resource adapter's 

ra.xml deployment descriptor. For example, 

 

COMSResourceAdapter 

 

 

RmiRegistryPort 

java.lang.String 

10990 

 


RmiRegistryPort configuration property needs to be configured if 

the RMI registry port number containing the TIP server is not the 

1099 default port. 

For JBoss, the following change will need to be made to the 

XAResourceRecovery entry in the jbossjta-properties.xml file: 

 


registry containing the TIP server - this is only required if 

the registry port is not the 1099 default port number. 

For example, 

 

The process for configuring the port numbers used by the RMI 

registry and RMID is summarized below: 

1) Update the startTIP script: 

Use the rmiRegistryPort option to specify the port number that 

the RMI registry is started on, and rmidPort option to specify 

RMID's internal RMI registry 

2) Update the ra.xml deployment descriptor 

Add an entry for the RmiRegistryPort configuration property 

with the property's value set to the location of the RMI 

registry containing the TIP server reference. 

3) Update jbossjta-properties.xml (JBoss users) 


registry port number containing the TIP server reference. 


Annotation Information 

SYMPTOMS: 

Common Client Interface (CCI) Records are the only data structures 

supported by the connector for Java to MCP communications. 

156 6875 9497–003



New for 13.0 are annotations that allows any JavaBean or plain 

old Java object (POJO) to be used as a data structure in Java to 

MCP communications. 

Four annotations are provided by the Connector for mapping Java 

properties to COBOL data items. These annotations are listed 

below: 

- @Record 

Marks a JavaBean/POJO as a supported data structure 

- @AlphaNumericField 

Specifies character data mapping requirements 

- @NumericField 

Specifies numeric data mapping requirements 

- @RecordField 

Identifies an embedded JavaBean/POJO as a data structure 

These annotations are defined in the package 

com.unisys.coms.connector.annotation. A description of each 

annotation follows. 

Record Annotation (@Record) 

--------------------------- 

@Record is used to identify a JavaBean/POJO as a supported data 

structure. This annotation is required and is used at the class 

level. 

@Record has two optional attributes, name and description. 

- The name attribute is used to provide the data structure with 

a name. It defaults to the empty string (""). 

- The description attribute provides a short description for the 

data structure. It defaults to the empty string. 

In the following example, @Record is used to mark the object as a 

data structure supported by JRAC. 

import com.unisys.coms.connector.annotation.Record; 

@Record 

public class Customer { 

} 

In the next example, the name and description attributes are used 

with @Record. 


@Record (name="customer", description="customer information") 


} 

6875 9497–003 157


AlphaNumericField Annotation (@AlphaNumericField) 

------------------------------------------------- 

@AlphaNumericField is used to specify character data mapping 

requirements. 

This annotation plays the same role as COMSAlphaNumericField - the 

COMSAlphaNumericField properties are attributes in 

@AlphaNumericField (for example, fieldPosition and fieldSize). 

@AlphaNumericField can be specified at either the field or method 

level. 

@AlphaNumericField example 

In this example: 

- Customer.java is used to model the CUSTOMER 01 COBOL record. 

- An AlphaNumericField annotation is used to map the firstName 

property to the FIRST-NAME data item. 

The AlphaNumericField annotation used to identify this mapping 

is expressed as a field-level annotation. 

- A second AlphaNumericField annotation is used to map the 

lastName property to the LAST-NAME data item. 


is expressed as a method-level annotation. 

01 CUSTOMER. 

05 FIRST-NAME PIC X(20). 

05 LAST-NAME PIC X(20). 


import com.unisys.coms.connector.annotation.AlphaNumericField; 

@Record 


@AlphaNumericField(fieldPosition=0, fieldSize=20) 

private String firstName; 

private String lastName; 

private String getFirstName() { 

return firstName; 

} 

private void setFirstName(String firstName) { 

this.firstName = firstName; 

} 

private String getLastName() { 

return lastName; 

158 6875 9497–003

} 

} 


private void setLastName(String lastName) { 

this. lastName = lastName; 

} 


NumericField Annotation (@NumericField) 

--------------------------------------- 

@NumericField is used to specify numeric data mapping requirements. 

This annotation plays the same role as COMSNumericField - the 

COMSNumericField properties are attributes in @NumericField (for 

example, fieldPosition, digitsLeft, and digitsRight). 

@NumericField can be specified at either the field or method 

level. 

@NumericField example 



- A NumericField annotation is used to map the identification 

property to the CUSTOMER-ID data item. The annotation is 

expressed at the field-level. 

01 CUSTOMER. 

05 CUSTOMER-ID PIC 9(12). 


import com.unisys.coms.connector.annotation.NumericField; 

@Record 


@NumericField(fieldPosition=0, digitsRight=12, digitsLeft=0) 

private long identification; 

} 

private long getIdentification () { 

return identification; 

} 

private void setIdentification(long identification) { 

this.identification = identification; 

} 

RecordField Annotation (@RecordField) 

------------------------------------- 

@RecordField is used to identify an embedded JavaBean/POJO as a 

JRAC supported data structure. 

6875 9497–003 159


This annotation plays the same role as COMSRecordField. 

@RecordField can be specified at either the field or method level. 

@RecordField example 



- A RecordField annotation is used to identify the address 

property as a data structure supported by JRAC. 

01 CUSTOMER. 

05 ADDRESS. 

10 STREET PIC X(20). 

10 CITY PIC X(20). 

10 ZIP-CODE PIC X(11). 


import com.unisys.coms.connector.annotation.RecordField; 

@Record 


@RecordField(fieldPosition=0) 

private Address address; 

} 

private Address getAddress() { 

return address; 

} 

private void setAddress(Address address) { 

this. address = address; 

} 



@Record 

public class Address { 


private String street; 


private String city; 


private String zipCode; 

private String getStreet() { 

return street; 

} 

private void setStreet(String street) { 

this. street = street; 

160 6875 9497–003

} 

} 

private String getCity() { 

return city; 

} 

private void setCity(String city) { 

this. city = city; 

} 

private String getZipCode() { 

return zipCode; 

} 

private void setZipCode (String zipCode) { 

this.zipCode = zipCode; 

} 


Interaction Usage 

----------------- 

The method executeObject has been added to JRAC's Interaction 

class implementation to allow annotated data structures to 

participate in interactions between the Java and MCP environments. 

executeObject has the following signature: 

public void executeObject( 

InteractionSpec iSpec, 

Object inputRecord, 

Object outputRecord) 

Interaction Example: 

In this example, the method executeObject is used to send a 

customer object to a COMS program and return an Order object back 

to the caller. An embedded array is returned to the client 

program. 

public PurchaceOrders getPurchaceOrders(Customer customer) { 

Connection connection = null; 

boolean success = false; 

Order order = new Order(); 

try { 

connection = connectionFactory.getConnection(); 

COMSInteraction interaction = 

(COMSInteraction)connection.createInteraction(); 

success = interaction(comsIspec, customer, order); 

} catch (Exception e) { 

throw new EJBException(e.getMessage(); 

} finally { 

try { 

if (connection != null) { 

6875 9497–003 161


} 

} 

connection.close(); 

} 


} 

if (!success) { 

throw new EJBException("Interaction was not successful"); 

} 

return order.getPurchaceOrders(); 


Annotation Information 

SYMPTOMS: 

Common Client Interface (CCI) Records are the only data structures 

supported by the connector for Java to MCP communications. 


New for 13.0 are annotations that allows any JavaBean or plain 

old Java object (POJO) to be used as a data structure in Java to 

MCP communications. 

Four annotations are provided by the Connector for mapping Java 

properties to COBOL data items. These annotations are listed 

below: 

- @Record 

Marks a JavaBean/POJO as a supported data structure 

- @AlphaNumericField 

Specifies character data mapping requirements 

- @NumericField 

Specifies numeric data mapping requirements 

- @RecordField 

Identifies an embedded JavaBean/POJO as a data structure 

These annotations are defined in the package 

com.unisys.coms.connector.annotation. A description of each 

annotation follows. 

Record Annotation (@Record) 

--------------------------- 

@Record is used to identify a JavaBean/POJO as a supported data 

structure. This annotation is required and is used at the class 

level. 

162 6875 9497–003


@Record has two optional attributes, name and description. 

- The name attribute is used to provide the data structure with 

a name. It defaults to the empty string (""). 

- The description attribute provides a short description for the 

data structure. It defaults to the empty string. 

In the following example, @Record is used to mark the object as a 

data structure supported by JRAC. 


@Record 


} 

In the next example, the name and description attributes are used 

with @Record. 


@Record (name="customer", description="customer information") 


} 

AlphaNumericField Annotation (@AlphaNumericField) 

------------------------------------------------- 

@AlphaNumericField is used to specify character data mapping 

requirements. 

This annotation plays the same role as COMSAlphaNumericField - the 

COMSAlphaNumericField properties are attributes in 

@AlphaNumericField (for example, fieldPosition and fieldSize). 

@AlphaNumericField can be specified at either the field or method 

level. 

@AlphaNumericField example 



- An AlphaNumericField annotation is used to map the firstName 

property to the FIRST-NAME data item. 


is expressed as a field-level annotation. 

- A second AlphaNumericField annotation is used to map the 

lastName property to the LAST-NAME data item. 


is expressed as a method-level annotation. 

6875 9497–003 163


01 CUSTOMER. 

05 FIRST-NAME PIC X(20). 

05 LAST-NAME PIC X(20). 


import com.unisys.coms.connector.annotation.AlphaNumericField; 

@Record 



private String firstName; 

private String lastName; 

} 

private String getFirstName() { 

return firstName; 

} 

private void setFirstName(String firstName) { 

this.firstName = firstName; 

} 

private String getLastName() { 

return lastName; 

} 


private void setLastName(String lastName) { 

this. lastName = lastName; 

} 

NumericField Annotation (@NumericField) 

--------------------------------------- 

@NumericField is used to specify numeric data mapping requirements. 

This annotation plays the same role as COMSNumericField - the 

COMSNumericField properties are attributes in @NumericField (for 

example, fieldPosition, digitsLeft, and digitsRight). 

@NumericField can be specified at either the field or method 

level. 

@NumericField example 



- A NumericField annotation is used to map the identification 

property to the CUSTOMER-ID data item. The annotation is 

expressed at the field-level. 

164 6875 9497–003

01 CUSTOMER. 

05 CUSTOMER-ID PIC 9(12). 




@Record 


@NumericField(fieldPosition=0, digitsRight=12, digitsLeft=0) 

private long identification; 

} 

private long getIdentification () { 

return identification; 

} 

private void setIdentification(long identification) { 

this.identification = identification; 

} 

RecordField Annotation (@RecordField) 

------------------------------------- 

@RecordField is used to identify an embedded JavaBean/POJO as a 

JRAC supported data structure. 

This annotation plays the same role as COMSRecordField. 

@RecordField can be specified at either the field or method level. 

@RecordField example 



- A RecordField annotation is used to identify the address 

property as a data structure supported by JRAC. 

01 CUSTOMER. 

05 ADDRESS. 

10 STREET PIC X(20). 

10 CITY PIC X(20). 

10 ZIP-CODE PIC X(11). 


import com.unisys.coms.connector.annotation.RecordField; 

@Record 


@RecordField(fieldPosition=0) 

private Address address; 

private Address getAddress() { 

return address; 

} 

6875 9497–003 165


} 

private void setAddress(Address address) { 

this. address = address; 

} 



@Record 

public class Address { 


private String street; 

} 


private String city; 


private String zipCode; 

private String getStreet() { 

return street; 

} 

private void setStreet(String street) { 

this. street = street; 

} 

private String getCity() { 

return city; 

} 

private void setCity(String city) { 

this. city = city; 

} 

private String getZipCode() { 

return zipCode; 

} 

private void setZipCode (String zipCode) { 

this.zipCode = zipCode; 

} 

Interaction Usage 

----------------- 

The method executeObject has been added to JRAC's Interaction 

class implementation to allow annotated data structures to 

participate in interactions between the Java and MCP environments. 

executeObject has the following signature: 

public void executeObject( 

InteractionSpec iSpec, 

166 6875 9497–003

Object inputRecord, 

Object outputRecord) 

Interaction Example: 


In this example, the method executeObject is used to send a 

customer object to a COMS program and return an Order object back 

to the caller. An embedded array is returned to the client 

program. 

public PurchaceOrders getPurchaceOrders(Customer customer) { 

Connection connection = null; 

boolean success = false; 

Order order = new Order(); 

} 

try { 

connection = connectionFactory.getConnection(); 

COMSInteraction interaction = 

(COMSInteraction)connection.createInteraction(); 

success = interaction(comsIspec, customer, order); 


throw new EJBException(e.getMessage(); 

} finally { 

try { 

if (connection != null) { 

connection.close(); 

} 


} 

} 

if (!success) { 

throw new EJBException("Interaction was not successful"); 

} 

return order.getPurchaceOrders(); 


New Product Name 

SYMPTOMS: 

The product's name, J2EE Connector for MCP Transactions, does not 

follow the Java (or Sun Microsystems) naming policy. 


The product has been renamed MCP Transaction Resource Adapter for 

the Java Platform. This name meets the Java (or Sun Microsystems) 

naming policy. 

6875 9497–003 167



New Product Name 

SYMPTOMS: 

The product's name, J2EE Connector for MCP Transactions, does not 

follow the Java (or Sun Microsystems) naming policy. 


The product has been renamed MCP Transaction Resource Adapter for 

the Java Platform. This name meets the Java (or Sun Microsystems) 

naming policy. 

KEYEDIOII 

Component: KEYEDIOII PRI-11537138 

Clarification to the Setting of NORECOVERY Attribute 

SYMPTOMS: 

The sentence in D-Notes of PRI-7086555 contradicts following 

existing sentence in the KEYEDIOII manual page 6-5: 

" 

When more than one user is accessing a file and one of the 

users sets the NORECOVERY attribute to FALSE, update transactions 

continue to be written to the audit file, even if other users 

have set the NORECOVERY attribute to TRUE. 

" 


Remove the following bullet on page 6-5 under the heading 

"Running the System without Auditing" from the KEYEDIOII 

Programming Reference Manual, (document # 8600 0684). 

. When more than one user is accessing a file and one of the 

users sets the NORECOVERY attribute to FALSE, update 

transactions continue to be written to the audit file, even 

if other users have set the NORECOVERY attribute to TRUE 

168 6875 9497–003

LICENSECENTER 

Component: LICENSECENTER PRI-11428894 

Comparison Between Keys Files 


SYMPTOMS: 

Currently, there is no option in LicenseCenter to compare 

Keys Files. 


An option for comparing two Keys Files has been added to 

LicenseCenter. A comparison wizard is added to get the type of a 

comparison users wants to perform and a tree node is added for each 

comparison where user can see the result of the comparison. 

Also there is an option to export the Comparison Result. 


License Center Help Update for 12.1 ERD 

SYMPTOMS: 

License Center help update for 12.1 ERD. 




Add x64 Support 

SYMPTOMS: 

After running the .msi file for MCPNEIGHBORHOOD, the installation 

completes successfully, but no Icon appears on the Desktop; neither 

does it appear in Windows Explorer, so connecting from the Windows 

to the MCP environment is not possible. 


By default, the Security Center installation installs a 32-bit 

version of MCP Neighborhood Windows Explorer Extension. On x64-based 

versions of Windows, a 64-bit MCP Neighborhood is needed in order to 

browse the MCP Environment through 64-bit Windows Explorer. The 

64-bit version of MCP Neighborhood can be found on the INSTALLS share 

in the directory MCPNeighborhood as MCPNghbrhdx64.msi. 

6875 9497–003 169


(An upgrade to the latest version of NX/Services may be required 

to install this file). Both 32-bit and 64-bit MCP Neighborhood 

Windows Explorer Extensions can be present on the same system. 

32-bit applications (such as License Center) use the 32-bit 

version, and 64-bit applications (such as Windows Explorer) use the 

64-bit version. 


License Center Help Update for 12.1 ERD 

SYMPTOMS: 




Component: LICENSESUPPORT PRI-11485278 

Allow Progress Interrogation for Nightly Detail Delete Task 

SYMPTOMS: 

A customer reported that the nightly deletion task that removes 

old recrods from the Licensesupport database was running longer 

than expected. It was not obvious whether the task was looping or 

whether there were simply a large number of deletion cantidates to 

be processed. 


An AX command to the SYSTEM/LICENSESUPPORT/NIGHTLY/DETAIL/DELETE 

task will now return a progress indication. 

Component: LICENSESUPPORT PRI-11486177 

Allow Progress Interrogation for Nightly Detail Delete Task 

SYMPTOMS: 

A customer reported that the nightly deletion task that removes 

old recrods from the Licensesupport database was running longer 

than expected. It was not obvious whether the task was looping or 

whether there were simply a large number of deletion cantidates to 

be processed. 

170 6875 9497–003



An AX command to the SYSTEM/LICENSESUPPORT/NIGHTLY/DETAIL/DELETE 

task will now return a progress indication. 

LOAD-UTILS 

Component: LOADER PRI-11469027 


SYMPTOMS: 

















LOG-TOOLS 

Component: JOBFORMATTER PRI-11437877 

System Option ENABLEPOSIX is Deimplemented 


The ENABLEPOSIX system option has been deimplemented. The system 

will now behave as if the option is set; this has been the behavior 

since MCP 45.1. 

6875 9497–003 171



Remove Support For LDML 


The LOADMICROCODE command is no longer supported. 



SYMPTOMS: 


















Override Operator RSVP During RY and SV of CPM 

SYMPTOMS: 

When a CPM is readied or saved (RY CPM n, SV CPM n), operator 

intervention is required to respond to the RSVP: 

SYSTEM MAY PAUSE SEVERAL MINUTES DURING RECONFIGURATION (OK OR DS) 

172 6875 9497–003



You can now use the NOW option with the SV and RY system commands to 

cause the reconfiguration action to take place without operator 

intervention. 

The commands have the following syntax when applied to a CPM: 

---+-- RY --+----- CPM ---- ---+-----------+-----| 

| | | | 

+-- SV --+ +-- : NOW --+ 

If the NOW modifier is used, the CPM will be readied or saved 

without additional operator input. Note that the operation will 

result in the system pausing during reconfiguration. 


New SYSOPS LMCDMULTIVOLUME and HLWAITFAMINDEX 

SYMPTOMS: 

At halt load time disk families can come online even if some 

continuation disks are not online. 

It is a nuisance to have to specify MULTIVOLUME when copying 

to CDs. 


You can set the system option HLWAITFAMINDEX to force the halt load 

process to wait for any missing continuation packs of families with 

online base packs. 

You can set the system option LMCDMULTIVOLUME to force the default 

value of MULTIVOLUME to TRUE for copies of files with Library 

Maintenance to a CD. 


Daily Warning of Imminent Key Expiry 

SYMPTOMS: 

When license keys expire, products may no longer work. There is no 

warning of imminent key expiry which would allow corrective action 

to take place prior to the keys actually expiring. 


Daily warnings are now generated when the system keys file contains 

6875 9497–003 173


keys that are due to expire in the near future. The warning message 

is: 

n temporary license keys will expire within the next m days. 

Use the LS TEMP system command or License Center to list 

temporary keys. 

where n is the number of keys affected and m is a configurable 

number of days. 

The LS (License Status) system command can be used to configure and 

display the number of days for which warnings are generated. 

The syntax of the LS TEMPORARY option allows the WARNFACTOR to be 

specified: 

--- LS --- TEMPORARY --- WARNFACTOR --+-- --+--------| 

+---- - -----+ 

LS TEMPORARY WARNFACTOR 

Sets the number of days warning prior to key expiry. 

is a number between 0 and 127. Setting WARNFACTOR to 0 disables 

the generation of warnings. 

LS TEMPORARY WARNFACTOR - 

Sets the number of days warning prior to key expiry to the 

default value (30 days). 

GETSTATUS/SETSTATUS Changes 

SETSTATUS Type 2 (Miscellaneous Request), Subtype 111 

Use this SETSTATUS request to set the WARNFACTOR associated with 


Input 

Use the following input for this call: 

Call 

Parameter Value or Description 

TYPE 2 

SUBTYPE 111 

VAL 1 = Set LS TEMP WARNFACTOR 

ARRAYROW A [0] = 3 

A [1] = 0 & 1 [38:06] 

A [2] = Number of days warning. If this 

value is -1, WARNFACTOR is set 

to 30 days 

174 6875 9497–003

RSLT := SETSTATUS (2, 111, 1, A); 

Results 


SETSTATUS does not return any unique soft errors for this call. 

Example 

For the system command LS TEMP WARNFACTOR 90, use the following 

input: 

A [0] := 3; 

A [1] := 0 & 1 [38:06]; 

A [2] := 90; % Days 


GETSTATUS Type 2 (Miscellaneous Request), Subtype 1 (Operations) 

The current LS TEMP WARNFACTOR is returned when mask bit 32 is 

set in a subtype 1 call. The description of mask bit 32 now 

includes: 

MASK Bit Description 

32 State bits. 

[47:02] Value of the AUTORESTORE archiving 

option 

0 = DONTCARE 

1 = NEVER 

2 = YES 

[19:01] LS TEMP WARNFACTOR validity 

[18:07] LS TEMP WARNFACTOR value 

SYSTEMSTATUS Changes 

The current LS TEMP WARNFACTOR is returned in the General 

Operating System Information section of the Software Configuration 

(Type 17) call. 

Word Field Type Name and Meaning 

64 07:01 B LS TEMP WARNFACTOR validity 

06:07 I LS TEMP WARNFACTOR value 

System Message Support Manual Changes 

One temporary license key will expire within the next 

days. Use the LS TEMP system command or License Center to list 

temporary keys (KF119) 

and 

temporary license keys will expire within the next 

days. Use the LS TEMP system command or License Center 

6875 9497–003 175


to list temporary keys (KF119) 

The variable is a number. The variable is the 

number of license keys. 

Cause 

A temporary license key (a license key with an expiration date) 

will expire soon. This message is generated daily, at midnight. 

Response 

To determine the license keys that will expire, use the LS TEMP 

system command, or use License Center. If the license key is 

active, then contact your Unisys sales office to renew the key. 

If you no longer need the key, use the IK DELETE command 

to delete the key, or use the Delete function from License 

Center. Reply OK to the RSVP. 

You can configure the number of days of warning. The default 

value is 30 days. You can use the LS TEMP WARNFACTOR system 

command to set the value between 1 and 127. If you set the 

value to 0, the warning mechanism will be disabled. 


Allow Comment With REMOTEUSER Definition 

SYMPTOMS: 

It is sometimes difficult to maintain REMOTEUSER entries because 

there is no facility to add comments to specific entries. Such 

comments can be associated with USER entries using existing text 

user attributes or by extending the USERSTRUCTURE. 


A comment can now be associated with specific REMOTEUSER entries. 

The comment is intended for documentation purposes only; it has no 

effect on the behavior of a REMOTEUSER entry. The comment will be 

shown in response to a MAKEUSER REMOTEUSER interrogation and 

displayed in the Remote Users result pane by Security Center. 

The comment is a string up to 100 characters long. 

MAKEUSER Changes 

================ 

In MAKEUSER, the remoteuser add and modify statements now allow an 

optional COMMENT entry, in addition to the existing optional SERVICE 

and LOCALALIAS entries. 

For example, 

176 6875 9497–003

+ RU JONESSM OF NXSERVICES LOCALALIAS = JONES 

COMMENT = "S M Jones from Accounting"; 

is valid syntax. 


In Security Center, the comment field is displayed in a column in 

the Remote Users pane. An edit box is provided to allow a comment 

to be added, modified or deleted on the Add New Remote Entry, Modify 

Remote Entry, and Clone Remote User dialogs. 

Note: A REMOTEUSER entry that includes a comment cannot be 

recognized by an MCP that does not support the comment 

attribute. Any service list associated with such a 

REMOTEUSER entry will be ignored by an old MCP, and it 

will be lost if a COPY NEW operation is performed. 

USERDATA Changes 

================ 

You can determine whether the MCP supports the new functionality 

with USERDATA function 3, subfunction 3. Bit 44 of the USERDATA 

result is set if the MCP supports the comment attribute. 

The behavior of USERDATA function 13, subfunctions 0, 2, and 3 has 

been changed to return the comment as part of the inquiry response. 

Set the RUSEREXTF ([23:01]) bit in the ACTION word to enable the 

new behavior. If RUSEREXTF is set, the service list mask and 

comment are returned in a structure which is placed after any 

hostname. To locate the attribute structure, subtract the 

UDVSERVLENF field from the UDVRULENF field. Note that UDVSERVLENF 

has been changed from [31:04] to [35:08]. 

The structure is formatted as: 

Word Description 

n Bit mask where 

bit 0 = service list mask present 

bit 1 = comment present 

n+1 Link to service list mask 

n+2 Link to comment 

Links consist of two fields: 

Field Description 

19:20 Offset from word n to data 

39:20 Length, in characters, of data 

The standard form name stored in a REMOTEUSER entry structure now 

has an additional node: 

Node Item 

1 Local alias 

2 Host name, domain name, or IP Address 

6875 9497–003 177


3 Optional service list mask 

4 Optional comment 

Note that if the optional comment is present, the optional service 

list mask will also be present. The mask 4"FFFFFF000000" represents 

the default (that is, an empty service list). 


Audit Changes to System Maintained Usercode Attributes 

SYMPTOMS: 

When the system updates a user entry as a by-product of some other 

action, the change to the user entry is not audited. For example, 

if the SAVELASTAUTHEN usercode attribute is TRUE and the usercode 

password is successfully validated, the user entry is updated to 

reflect the time of the authentication, but there is no entry in 

the system log for the change. 


A new log entry, major type 6, minor type 23 is now written when a 

user entry is updated as a result of a system initiated activity. 

Such activities include updating user history profile attributes 

such as LASTLOGONTIME, and changes as a result of password 

migration. 

The layout of a major type 6, minor type 23 (USERDATA Change of 

System Maintained Attribute) log entry is identical to the existing 

major type 6, minor type 9 (USERDATA Change) log entry. However, 

the USERDATA function (stored in field [03:04] of word 4) may be 3 

(Validate Usercode/Password) in the new entry. This is in addition 

to the existing USERDATA functions. 

The following explanation will be added to the System Log 

Programming Reference Manual (form # 8600 1807). 

Major Type 6 - Minor Type 23 (USERDATA Change of System Maintained 

Attribute) 

The Major Type, Minor Type 23 entry contains information about 

USERDATA changes that have been initiated by the system. 

Use the USERDATA option in LOGANALYZER to obtain a report that 

contains information about all the USERDATAFILE changes. 

The following table describes the format and contents of this 

entry. 

Word Field Value Description 

0-3 Standard layout of first four log entry 

178 6875 9497–003

words 

4 [03:04] USERDATA function 

3 Validate Usercode/Password 


5 LINK to information. Attribute changes in 

USERDATAREBUILD format 

6 Original location of entry 

7 Final location of entry 

8 Size of entry (in words) 

9-end Variable-length data pointed to by the 

LINK in this entry 

The descriptions for words 4 and 5 should be merged with the 

existing descriptions for a major type 6, minor type 9 record. 

If the LOGGING option is set to DEFAULT or MINIMAL, these log 

entries will be logged to the sumlog. 


Documentation for RBAC Logging 


The new LOGANALYZER option RBAC selects records created by 

the Role Based Access Control library RBACSUPPORT. 

The new LOGANALYZER DIAGNOSTICS option RBAC selects error records 

created by the Role Based Access Control library RBACSUPPORT. 

Make changes to the "LOGANALYZER" section of the "System Software 

Utilities Operations Manual" as follows. 

In the "Diagnostics Options" sub-section, add the following 

rail to the DIAGNOSTICS railroad diagram: 

|-- /1\ -- RBAC ---| 

In the "Explanation" that follows replace the last sentence of 

the second paragraph (replace "Note that the SNA minor type has 

no subtypes") with 

Note that the RBAC and SNA minor types have no subtypes. 

Add RBAC to the un-named table that follows: 

Refer to minor type number ... For a description of... 

6875 9497–003 179


40 RBAC (Role Based Access 

Control) entries 

In the "Additional Selection Options" sub-section make the 

following changes. Add the following rail to the railroad diagram: 

|-- /1\ -- RBAC ---| 

Under "Explanation" add the following: 

RBAC 

Lists entries associated with the successful completion of 

administrator procedures in the RBACSUPPORT library. 

Make changes to the "System Log Programming Reference Manual" as 

follows. 

Add the following new sub-section to section 10 "Major Type 6 

Miscellaneous Entry": 

Major Type 6-Minor Type 24 (Role Based Access Control Entry) 

The Major Type 6 Minor Type 24 entry contains information about 

the successful completion of adminstrator procedures in the 

RBACSUPPORT library. 

Use the RBAC option in LOGANALYZER to see these entries. 

The following table describes the format and contents of the 

entry. The length in the LINKs is the number of characters in 

the name. 

Table Major Type 6-Minor Type 24 (LOGMIN_RBAC) 


0-3 As described in Table 2-1, "First 

Four Log Entry Words Version 0 

Format" or Table 2-2, "First Four 

Log Entry Words Version 1 Format" 

4 Procedure number 

1 CREATE_REALM 

2 DELETE_REALM 

3 ADD_REALM_ADMINISTRATOR 

4 DELETE_REALM_ADMINISTRATOR 

5 ADD_ROLE 

180 6875 9497–003

6 DELETE_ROLE 

7 ADD_PERMISSION 

8 DELETE_PERMISSION 

9 ADD_PERMISSION_TO_ROLE 


10 DELETE_PERMISSION_FROM_ROLE 

11 ADD_USER_TO_ROLE 

12 DELETE_USER_FROM_ROLE 

17 SET_CURRENT_ROLE 

5 Realm Id or 0 

6 0 or LINK to Realm Name 

7 Role Id or 0 

8 0 or LINK to Role Name 

9 Permission Id or 0 

10 0 or LINK to Permission Name 

11 0 or LINK to User Name or LINK to 

Administrator Name 

Make changes and additions to section 21 "Major Type 19 Diagnostic 

Entry" as follows. 

Add the following Minor Type to the bullet list of Minor Types 

Minor Type 40-Role Based Access Control (RBAC) (LOGDIAG_RBAC) 

In "Table 21-1. Major Type 19-All Minor Types", 

after the line that reads "4 Specialized IPTRACE format", add 

the following new line. 

5 Specialized RBAC format 

Then change "5-15" to "6-15" in the next line. 

Add the following to "Table 21-2. Subtype Values by Minor Type": 

Minor 

Type Identifier Subtype JOBFORMATTER Meaning 

40 Role Based Access 0 none Procedure name 

Control (RBAC) and error text. 

6875 9497–003 181



New Security Option SECURECOMM 


A new security option, SECURECOMM, controls whether some services 

offer connections over a secure communications channel or not. 

This security option currently only affects Telnet behavior. 

The SECURECOMM security option can be set to DISABLED, ALLOWED, 

or REQUIRED: 

SECOPT SECURECOMM DISABLED 

Telnet only offers connections over the non-secure port 

(default port number 23) 

SECOPT SECURECOMM REQUIRED 

Telnet only offers connections over the secure port (default 

port number 992) 

SECOPT SECURECOMM ALLOWED 

Telnet offers connections over both the secure port (default 

port number 992) and the non-secure port (default port number 

23) 

The value of the SECURECOMM option can be found in the second 

security option word: 

Field [27:3] SecureComm 

0 = Allowed 

1 = Disabled 

3 = Required 








or REQUIRED: 


Telnet only offers connections over the non-secure port 

182 6875 9497–003

(default port number 23) 








23) 




0 = Allowed 

1 = Disabled 

3 = Required 


DMS Logging 


Database Opens and CLoses are logged against the stack containing 

the database declaration. The log record now contains details 

of the stack invoking the Open or Close. 

Database Resumes are logged against the database stack. The log 

record now contains details of the stack causing the resume to 

occur. 

Make these changes to Section 5 of the System Log Programming 

manual : 

In Table 5-15 : 

Replace the description of Word 10 by "Unused" 

Replace the information for Word 13 onwards by : 

13 [38:39] Database stack number 

14 [38:39] Database job number 

15 [38:39] Database task number 

16 [38:39] Actor stack number 

17 [38:39] Actor task number 


LINKs in this entry 


6875 9497–003 183



6 Unused 


8 Obsolete information 

9 [38:39] RESUME Actor stack number 

10 [38:39] RESUME Actor task number 


DMS Logging 







occur. 


manual : 













6 Unused 





184 6875 9497–003


Log Inquire Permission Failures 


SYMPTOMS: 

If an INQUIRE_PERMISSION call indicates that the task does not have 

the requested permission, this may be an indication of violation of 

role policy. This violation should be logged. 


If the PERMISSIONID parameter passed to INQUIRE_PERMISSION (or 

INQUIRE_PERMISSION_FOR_TASK) is a negative value, a Major Type 6, 

Minor Type 24 (Role Based Access Control) log entry is generated. 

The description of the log entry in the System Log Programming 

Reference manual (form # 8600 1807) is updated as follows: 

Word 4, Value 20, INQUIRE_PERMISSION 

Word 12, Mix number or 0 

For INQUIRE_PERMISSION, a mix number is stored (if the task 

supplied is an active task). 

Component: LOGANALYZER PRI-11444261 

Allow More FIND Targets 

SYMPTOMS: 

Only 10 FIND targets can be specified. 


You can now specify up to 100 FIND targets. Note that there is an 

impact on processing time the more FIND targets that are specified. 

Update the System Software Utilities Operations Reference Manual 

(form # 8600 0460) as follows: 

In the definition in the Selection Options topic 

of the LOGANALYZER section, change "10*" to "100". 

6875 9497–003 185



Allow Filtering On More Than One Usercode 

SYMPTOMS: 

When SYSTEM/IGSDASUPPORT is installed as the SDASUPPORT library, a 

user with direct read access to the log can use the UC or USERCODE 

LOGANALYZER option to limit the entries analyzed from the log to a 

specific usercode. 

However, it is not possible to specify a list of usercodes for 

which filtering is desired. 


The USERCODE (UC), ACCESSCODE (AC) and CHARGECODE (CC) LOGANALYZER 

options can now be followed by a list of identifiers. If more than 

one identifier is specified, the log will be filtered to show 

entries for all identifiers in the list. The special identifier 

"." is incompatible with a list (because it indicates that no 

filtering is desired). 

Modify the "Selection Options" topic of the "LOGANALYZER Options" 

topic of the "LOGANALYZER" section of the System Software Utilities 


Change the railroad diagram for the 

ACCESSCODE, CHARGECODE, and USERCODE bars to include a metatoken 

and to add a /1\ bridge at the beginning. 

The metatoken is defined as: 

+----------- , ------------+ 

| | 

----------+----


Allow Selection of INSTALLATION Log Records 


SYMPTOMS: 

INSTALLATION log records cannot be explicitly selected for 

analysis. 


INSTALLATION log records (major type 7) can now be selected for 

analysis by LOGANALYZER. 

The following changes should be made to the LOGANALYZER section 

of the System Software Utilities Operations Reference Manual 

(form # 8600 0460). 

Add another entry to : 

INST 

INSTALLATION 

---+--- INST -----------+------------------- 

| | 

+--- INSTALLATION ---+ 

Selects site defined installation log entries for analysis. If 

the SITESUPPORT library is not present or the PINSTALLATION 

function of the SITESUPPORT library indicates that the log entry 

has not been analyzed, the log entry will be dumped in 

hexadecimal form. 


TRUNCATE Option Limits Number of Lines Per Entry 

SYMPTOMS: 

LOGANALYZER output can be quite voluminous because of the number of 

output lines required to fully analyze some log records. 


You can now use the TRUNCATE output option to specify the maximum 

number of output lines used when analyzing each log entry. 

Add the following to the System Software Utilities Operations 

Reference Manual (form # 8600 0460) 

In the Output Options topic of the LOGANALYZER Options topic in the 

6875 9497–003 187


LOGANALYZER section, extend the syntax diagram 

with: 

---- TRUNCATE ----+-----------------+---------------- 

| | 

+--- ---+ 

Explanation 

TRUNCATE 

Limits the number of lines of output produced for each log entry 

to the specified value. The default value, used if none is 

specified, is 1. 

Note: When the TRUNCATE option is set, output lines that would 

normally be wrapped (because of the width of the display) will 

be truncated. 


Analysis & Description of CIA Dialog and Node Records 


Update SYSTEM LOG PROGRAMMING REFERENCE MANUAL 

Section 33 Major Type 36 - FastPath CIA Information Logging 

Major Type 36-Minor Type 4 (CIA Node Information) 

Modify Table describing the format and contents of the entry: 


---- ----- ----- ----------------------------- 

19 

5 ULM Event 

The following words are valid if the node action is 

ULM Event 

27 ULM Reason 

1 Invalid Message 

2 Invalid Dialog Id 

3 Error Message Received 

4 Invalid Message Type 

5 Error Message Sent 

6 Message Not Sent 

7 Rescind Message Sent 

8 Debug text 

188 6875 9497–003


28 The LINKREFERNCE word that points to 

the ULM Information: This is variable 

data that can be used to diagnose the 

context of the ULM Event occurrence. 

29- Variable-length data. Contains the data 

end pointed to by the LINKREFERENCE words 

in this entry. 

Major Type 36-Minor Type 5 (CIA Dialog Information) 

Modify Table describing the format and contents of the entry: 


---- ----- ----- ----------------------------- 

19 

7 Event 

21 Dialog State, valid if dialog action is event. 

22 Client Access Indicator 

0 Client attached 

1 Client shut out (has delinked) 

23-25 ** shift the existing descriptions for words 22 - 24 ** 

The following word is valid if the dialog action is 

Faulted, Closed, Destroyed 

26 Termination Reason 



The following word is valid if the dialog action is event. 

39 Event reason. 

0 Commence Creation, 

1 Fault - No State Change, 

2 Commence Destroy, 

3 Commence Opening, 

4 Remote Close - Ignored, 

5 Remote Close - Reported, 

6 Rescind Match Request, 

7 Send Match Error, 

8 Match Error Message Recieved, 

9 Stale Error Message Recieved, 

10 Aborting Dialog Connection, 

11 Match Accept Received - Improper Dialog State 

12 Rescind Confirm Received - Improper Dialog 

State 

6875 9497–003 189


40- Variable-length data. Contains the data 

end pointed to by the LINKREFERENCE words 

in this entry. 


Update System Commands Allowed With OPERATOR Option 

SYMPTOMS: 

Many new commands cannot be used with the OPERATOR option. 


The list of commands that can be specified with the LOGANALYZER 

OPERATOR option has been expanded to include some recent system 

commands that were unintentionally omitted, and to remove some 

obsolete commands. 

Note that a side effect of this change means that commands now 

need to be spelled in full (previously only the first six 

characters of long system commands were required.) 


Add PIO to Diagnostics Options 

SYMPTOMS: 

PIO was not included in the DIAGNOSTICS OPTIONS documentation. 


Add PIO to LOGANALYZER documentation as follows: 

In the "DIAGNOSTICS" railroad diagram add PIO. 

|--/1\ -- OSI ------| 

|--/1\ -- PIO ------| 

|--/1\ -- PS -------| 

In the table of minor type numbers corresponding to each 

DIAGNOSTICS option add an entry for PIO after the entry for OSI. 

31 PIO (Physical IO) log entries 

190 6875 9497–003




SYMPTOMS: 












migration. 








Programming 

Reference Manual (form # 8600 1807). 


Attribute) 






entry. 



words 





6875 9497–003 191












Log Enhancements for Workload Management 


Additional information is now stored in a major type 1 (Job or Task 

Entry), minor types 2 (EOJ) and 4 (EOT) records. A new log record, 

major type 1 (Job or Task Entry), minor type 24 (Task Interval), 

records the current values of many of the EOJ and EOT items. Both 

of these enhancements are intended to be used by the Workload 

Management assisted workload discovery feature, but are available 

for general use. 

The following items have been added to the EOJ and EOT records: 


71 LINK to IDENTITY code file attribute (standard 

form) 

72 LINK to source MCS name (standard form) 

73 LINK to MPID task attribute (substandard form) 

74 LINK to WORKLOADGROUP code file attribute 

(standard form) 

75 LINK to WORKLOADGROUP task attribute 

(substandard form) 

The layout of the Task Interval record is identical to the EOJ and 

EOT records, but only the following words are valid: 


192 6875 9497–003

4 Task Priority Information 


6 LINK to external name (standard form) 

7 LINK to usercode (standard form) 

8 LINK to charge code (standard form) 

24 LINK to access code (standard form) 

46 Stack number 

49 LINK to code file name (standard form) 

60 Processor set information 


form) 







Interval log records are written at most every 2 hours (the actual 

interval depends on the process activity). If LOGGING is set to 

DEFAULT, interval log records will be written only to the sumlog. 

If LOGGING is set to MINIMAL, interval log records will not be 

written. 













6875 9497–003 193



form) 



















form) 











written. 

194 6875 9497–003













|-- /1\ -- RBAC ---| 











|-- /1\ -- RBAC ---| 


RBAC 




follows. 




6875 9497–003 195








the name. 












5 ADD_ROLE 

6 DELETE_ROLE 












196 6875 9497–003
















Minor 





System Info returns information about networking data path 

interface 


Networking software components, e.g. SYSTEM/CNSSUPPORT, 

SYSTEM/BNA/SUPPORT and SYSTEM/TCPIPSUPPORT use a variety of 

methods to deduce how to communicate with outboard components. 

SYSTEM_INFO is expanded to report what methods are available on 

the running system. Networking software may use this information 

to initialize the appropriate methods. Note, this only reports 

the availability of a method not whether any networking device is 

employing the method. 

6875 9497–003 197




interface 










MARC 

Component: MARC PRI-11469051 


SYMPTOMS: 

















198 6875 9497–003




SYMPTOMS: 



















SYMPTOMS: 














6875 9497–003 199







SYMPTOMS: 



















SYMPTOMS: 










200 6875 9497–003










DNOTE: Some Log Specs Missing In MARC's LOGGING Command 

Display 

SYMPTOMS: 

This is a duplicate of the text from LOGGING/UPDATE/2, for 

Documentation's sake. 

Previously, some recent additions to the log types were not 

displayed in the output to the MARC LOGGING command. 

Likewise, the same log types weren't present on their respective 

menus. 

Specifically, the missing log types were: 

On the LOGJOB menu - 

(1,31) Library Delinkage Errors 

(1,32) Controlcard Tracking Data 

On the LOGMAINT menu - 

(2,31) Processor Performance Change Event 

(2,32) I/O Attribute Entries 

On the LOGMISC menu - 

(6,20) MessageSupport Command 

(6,22) Distributed Userdata 

No menu was provided for the following CSI log types: 

(32,1) Nexus Initialization 

(32,2) Nexus Termination Entries 

(32,3) Chrone Activate 

(32,4) Chrone Deactivate 

(32,5) Service Group Join 

(32,6) Service Group Leave 

(32,7) Trace Open Entries 

(32,8) Trace Close Entries 

6875 9497–003 201



Now, the LOGGING command displays all available valid log types. 

MCP 

The missing log types have been added to the LOGJOB, LOGMAINT and 

LOGMISC menus, and a LOGCSI menu is now available. 

Component: ATTABLEGEN PRI-11464521 


SYMPTOMS: 














SSLSECUREMODE 

============= 




Type Mnemonic 







202 6875 9497–003






=============== 









SSLCIPHERS 

========== 













Cipher Values 











6875 9497–003 203






=================== 



Modify Never 













Cipher Name 














SSLROOTSTORE 

============ 





204 6875 9497–003








SSLVERSION 

========== 



Modify Never 

Type Mnemonic 

Default Null 











SSLERROR 

======== 



Modify Never 

Type Integer 

Default 0 







6875 9497–003 205




Security SDK. 

SSLTYPE 

======= 




Type Mnemonic 














============ 







206 6875 9497–003













Component: CCTABLEGEN PRI-11417213 

Emit Warning If Predefined Word is Used 

SYMPTOMS: 

WFL should emit a warning if a predefined word is used. 

For example: 

BEGIN JOB; 

INTEGER COPY; 

COPY := 1; 

COPY X AS Y; 

END JOB. 


When a predefined word is used, the WFL compiler now gives the 

warning: 

USE OF PREDEFINED WORD COULD CAUSE UNEXPECTED RESULTS 

The Work Flow Language (WFL) Programming Reference Manual 

(8600 1047-508) needs to be modified as follows: 

In Appendix B. Reserved Words, Predefined Words, and Keywords; 

Reserved Words remove BINARY from the list of reserved words. 


Predefined Words add the following words to the list of 

predefined words in their proper alphabetical location: 

ALTER, ARCHIVE, CREATE, MKDIR, MOVE, REPLACE, RESTOREADD, 

RESTOREREPLACE, UNWRAP, VOLUME, WRAP. 

6875 9497–003 207


Component: CCTABLEGEN PRI-11487301 

Implement STARTTIME With Day of Week 

SYMPTOMS: 

STARTTIME should allow STARTTIME = ON . 

For example: STARTIME = 12:00 ON SATURDAY; 

This will cause the job to start on the next Saturday. If the 

current day is Saturday, then the job will start 7 days later. 


The STARTTIME specification is enhanced to allow TODAY, TOMORROW, 

the day of the week, and the day of the week with a month, day, and 

year. 

Please modify the Work Flow Lanaguage (WFL) Programming Reference 

Manual (8600 1047-509); Section 3. Job Structure; STARTTIME 

Specification as follows: 

Modify or add the following railroad diagrams: 

 

--+------------------+--+--------------------------------+--| 

| | | | 

+-- + ----+ +-- TODAY -----------------------+ 

| | 

+-- TOMORROW --------------------+ 

| | 

+-- ON --+-----------------+ 

| | 

+-- + ----+ 

 

--+-- -- / -- -- / --+-- ----+--------------+-----| 

| | | | 

| +-- --+ | 

| | 

+-- TODAY -----------------------------------------------+ 

| | 

+-- TOMORROW --------------------------------------------+ 

| | 

+-- ----+-----------------------------+----+ 

| | 

+--- ---+ 

 

--+-- SUNDAY -----+---| 

| | 

+-- MONDAY -----+ 

| | 

208 6875 9497–003

+-- TUESDAY ----+ 

| | 

+-- WEDNESDAY --+ 

| | 

+-- THURSDAY ---+ 

| | 

+-- FRIDAY -----+ 

| | 

+-- SATURDAY ---+ 

 


+ 

| | | | 

+--,--+ +--/1*\-- ---------+ 

>---+-----+----+-- ----+---------------------------------| 

| | | | 

+--,--+ +-- --+ 

should be added to the same diagram that contains 

, , and . 

 

--+-- JANUARY ----+---| 

| | 

+-- FEBURARY ---+ 

| | 

+-- MARCH ------+ 

| | 

+-- APRIL ------+ 

| | 

+-- MAY --------+ 

| | 

+-- JUNE -------+ 

| | 

+-- JULY -------+ 

| | 

+-- AUGUST -----+ 

| | 

+-- SEPTEMBER --+ 

| | 

+-- OCTOBER ----+ 

| | 

+-- NOVEMBER ---+ 

| | 

+-- DECEMBER ---+ 

In the Explanation text add the following information as a new 

paragraph before the last paragraph: 

If TODAY is specified, the current date is used. 

If TOMORROW is specified, one day is added to the current date. 

6875 9497–003 209


If a day of the week is specified, then enough days are added to 

the current date to start the job on the next day of the week 

that was specified. 

If a day of the week and a month, day, and year were specified then 

the system verifies that the specified date will fall on the 

specified day of week and that date is used. 

In the Examples text add the following examples and text: 

If the current day is Saturday, then the following job begins 

after 1:00 a.m. 7 days later than the current date. Otherwise, 

the job will begin after 1:00 a.m. on the next date that falls on a 

Saturday. 

?BEGIN JOB EXAMPLE; 

STARTTIME = 1:00 ON SATURDAY; 

. 

. 

. 

?END JOB. 

The following job begins execution after 2:00 p.m. on November 24, 

2008. 


STARTTIME = 14:00 ON MONDAY, NOVEMBER 24, 2008; 

. 

. 

. 

?END JOB. 

Component: CHECKPOINT PRI-11503608 

Improve CHECKPOINT and RESTART Messages 


Make changes to the "Task Management Programming Guide" 

form 8600 0494-508, as follows. 

Make changes to the "Checkpoint Completion Codes" table in the 

"Checkpoint Facility" sub-section of the "Restarting Jobs and 

Tasks" section as follows. 

Code 6: replace "#" with "NUMBER OF". 

Code 9: replace the message and explanation with the following: 

OPEN FILE WITH KIND= NOT ALLOWED 

Where is SC, REMOTE, CDROM, DATACOM/REMOTE, 

PORT, CDR, or FOREIGNTYPE/HOSTSERVICES. 

Code 10: delete this completion message. 

210 6875 9497–003



OPEN FILE WITH FILEORGANIZATION NOT 

ALLOWED 

Where is RELATIVE, INDEXED, 

INDEXDNOTRESTRICTED, PLIISAM, KEYEDIOII, 

KEYEDIOIISET, or KEYEDIOIISF. 



INVALID CONSTRUCT 

There is operating system code in the process stack, 

for example the SORT intrinsic. 

Code 23: replace "ILLEGAL" with "NOT ALLOWED". 


Code 28: delete this completion message 

Code 39: Add this new code with the message: 

ERROR OCCURRED DURING CHECKPOINT IN FILE 

The CHECKPOINT procedure encountered an error while 

trying to handle the indicated file. 

Add the following new codes and explanations: 

Code 56: CHECKPOINT ABORTED: ERROR TRYING TO ENTER CP FILE 

INTO THE DIRECTORY 


trying to store the checkpoint file into the SYSTEMDIRECTORY. 

Check for preceding directory error messages. 

Code 57: CHECKPOINT ABORTED: ERROR TRYING TO ENTER TEMPORARY 

FILE INTO THE DIRECTORY 


trying to store a temporary disk file into the 

SYSTEMDIRECTORY. 

Check for preceding directory error messages. 

Code 58: CHECKPOINT ABORTED: ERROR OPENING CP FILE 


creating the checkpoint file. For example, the DISK family 

or PACK family wasn't online. Check for preceding error 

messages. 

6875 9497–003 211


Code 59: CHECKPOINT ABORTED: I/O ERROR READING SEG0 OF FILE 

The CHECKPOINT procedure encountered an I/O error while 

reading SEG0 of a code file. Check for preceding I/O error 

messages. 

Code 60: CHECKPOINT ABORTED: ERROR COPYING OVERLAYED DATA TO 

CP FILE 

The CHECKPOINT procedure encountered an I/O error while 

reading data from a DL OVERLAY family or while writing overlay 

data to the checkpoint file. Check for preceding I/O error 

messages. 

Code 61: CHECKPOINT ABORTED: ERROR SETTING TITLE OF TEMPORARY 

FILE TO 'CP/number/number' 

This is an internal error, notify your UNISYS representative. 

Add the following new messages to the bullet list in the 

"Restarting a Checkpointed Task" sub-section of the 

"Restarting Jobs and Tasks" section of the manual. 

.RESTART ABORTED:IO ERROR READING FROM CHECKPOINT FILE 

Check for previous disk I/O error message that will indicate 

the I/O error encountered. 

.RESTART ABORTED:CODEFILE INCOMPATIBLE WITH MCP 

.RESTART ABORTED:USERCODE ERROR 

.RESTART ABORTED:IO ERROR READING SEG0 OF JOB FILE 



.RESTART ABORTED:IO ERROR READING SEG0 OF TASK FILE 



.RESTART ABORTED:IO ERROR READING SEG0 OF CODE FILE 



Make changes to the "System Messages Support Reference Manual" 

form 8600 0429-610 as follows. 

Add the following new messages and explanations. 

212 6875 9497–003


PK IO ERROR LRD= WRITING TO 

(MISC261) 

Where is either "FILE " or "JOB FILE ". 

Cause 

The indicated I/O error occurred while writing to the indicated 

disk file. The task may continue or terminate. 

Response 

Note error and observe if the task terminates. 

PK IO ERROR LRD= READING FROM 

(MISC262) 

Where is either "FILE " or "JOB FILE ". 

Cause 

The indicated I/O error occurred while reading from the indicated 

disk file. The task may continue or terminate. 

Response 

Note error and observe if the task terminates. 

CHECKPOINT ABORTED: (CP) 

Where "CP" is one of the following: 

CP1 thru CP9, CP11 thru CP17, CP19 thru CP26, 

CP30, CP32, CP34, CP36 thru CP61. 

Cause 

The program attempted to take a checkpoint or the operator entered 

a " BR" system command for the program, but the 

checkpoint attempt failed. The program continues to run. 

Response 

The describes the error. For more information about 

CHECKPOINT ABORTED messages refer to the "Checkpoint Facilty" 

sub-section of the "Task Management Programming Guide". 

Component: CONFIGURATION PRI-11413854 




6875 9497–003 213


Component: CONFIGURATION PRI-11445225 




Component: CONTROLLER PRI-11437711 







Y Response Shows Long Tape Operations In 

Progress 

SYMPTOMS: 

Certain tape operations, such spacing to EOF, can take a very 

long time to complete. During this time the program may appear 

to be "doing nothing" or "stuck" leading to it being DSed by 

an operator. 


The Stack State line Y response will include one of the following 

states: 

"Spacing to EOF" 

"Locating a block" 

"Locating End of Data" 

"Data Security Erase in progress" 

"Rewinding" 

214 6875 9497–003


Show Dates in Long Format in SQ Response 

SYMPTOMS: 

Need long dates in SQ response. 



The response to the SQ command now shows dates (queued date and 

start date) in long form. 

For example, an SQ command may generate: 

QUEUE 500 

3467 50 STARTTIMETEST 

QUEUED: Thursday, April 24, 2008 AT 12:11:51 

STARTTIME: Saturday, April 4, 2015 AT 14:55:00 

14341 50 STARTTIMETEST2 

QUEUED: Thursday, July 10, 2008 at 11:05:58 

STARTTIME: Today at 14:00:00 

245 50 STARTTIME/TEST/JOB 

QUEUED: Today at 09:30:31 

STARTTIME: Today at 15:35:00 

Additionally, when a start time is being set (with the STARTTIME 

system command), the date can now be specified as a long date or 

with just a day. 

Example 1: 

1234 STARTTIME = 10:00 ON FRIDAY 

will change the start time for the job to 10:00 on the next Friday. 

Example 2: 

1234 STARTTIME = 10:00 TODAY 

will change the start time for the job to 10:00 on the current day. 

Example 3: 

The system command 

1234 STARTTIME = 10:00 ON 5/30/2008 

can now be entered as 

1234 STARTTIME = 10:00 ON FRIDAY MAY 30 2008 

6875 9497–003 215



Allow FIND and SHOW to Use Relation For String Attributes 

SYMPTOMS: 

The FIND and SHOW commands allow the selection of entries based on 

attribute values. For a string valued attribute, you can include 

entries if the attribute matches a wild-card string. However, you 

cannot specify a negative match, whereas you can for other 

attribute types. 


For the FIND and SHOW commands, the definition of a for a string attribute is: 

|---- --+--------+--- ----| 

| | | | 

| +-- --+ | 

If the optional token is present, the selection includes any 

entry where the attribute does not match the wild card string. 


Override Operator RSVP During RY and SV of CPM 

SYMPTOMS: 

When a CPM is readied or saved (RY CPM n, SV CPM n), operator 

intervention is required to respond to the RSVP: 

SYSTEM MAY PAUSE SEVERAL MINUTES DURING RECONFIGURATION (OK OR DS) 


You can now use the NOW option with the SV and RY system commands to 

cause the reconfiguration action to take place without operator 

intervention. 

The commands have the following syntax when applied to a CPM: 

---+-- RY --+----- CPM ---- ---+-----------+-----| 

| | | | 

+-- SV --+ +-- : NOW --+ 

If the NOW modifier is used, the CPM will be readied or saved 

without additional operator input. Note that the operation will 

result in the system pausing during reconfiguration. 

216 6875 9497–003

Component: DATACOM PRI-11445624 

Revise documentation for MAXPSEUDO value limit 

SYMPTOMS: 

Syntax Error reply received for ID:MAXPSEUDO = 16383. 



System Commands Operations Reference and System Commands Help 

Change the third paragraph of the description for ID: MAXPSEUDO. 

The MAXPSEUDO variant of the ID command controls only 

pseudostations associated with the DATACOMINFO file, that is, 

those stations whose Logical Station Number (LSN) are numbered 

from 2 through 16383. Stations that are defined in the 

DATACOMINFO file and CANDE's Schedule stations are assigned 

numbers within this range. As ten (10) schedule stations are 

always provided, the maximum number value that may be specified 

is 16372. The actual number that are allocated is further 

reduced by the number of stations defined in the DATACOMINFO 

file. If you specify a nonzero value, the system allocates the 

pseudostations in the data comm information tables and in the 

DATACOMINFO file, the next time the data comm subsystem is 

initialized. Note that other system functions might be 

suspended while the pseudostations are allocated during 

initialization of the data comm subsystem, so an initial value 

should be chosen judiciously. 

Glossary items: 

Logical Station Number (LSN) 

A unique number assigned to each station in a network and each 

pseudostation allocated by a message control system (MCS). 

Each station has an LSN assigned according to the order in 

which the stations are defined. 

Message Control System (MCS) 

A program that controls the flow of messages between terminals, 

application programs, and the operating system. 

Schedule Station 

A dummy data communications station provided by the Command and 

Edit (CANDE) message control system to run schedule sessions. 

6875 9497–003 217


Component: DISKFILES PRI-11384293 

CHANGE and REMOVE Statements Return Result Information 

SYMPTOMS: 

WFL provides no method of determining whether a CHANGE or REMOVE 

was successful. 


The syntax of the CHANGE and REMOVE statements has been extended to 

allow the user to determine whether the action was successful and 

the nature of any failure. 

The CHANGE statement now allows up to 6 results to be returned and 

the REMOVE statement allows up to 5 results. The CHANGE statement 

can now be followed by an optional results structure -- [b1, i, b2, 

b3, b4, b5]. The REMOVE statement can now be followed by an 

optional results structure -- [b1, i, b2, b3, b4]. Parameters are 

optional, so for example [b1, i] is syntactically correct. 

However, if a parameter is specified, all preceding parameters must 

also be specified. The parameters return the following 

information: 

Variable Type Description 

b1 Boolean TRUE if a failure occurred. FALSE is all 

files and directories were changed or removed 

i Integer Total number of changed or removed files 

b2 Boolean TRUE if at least one file or directory was 

not removed or changed because it was not 

present 

b3 Boolean TRUE if at least one file was not removed or 

changed because the file was a locked file 

b4 Boolean TRUE if at least one file was not removed 

because of a security error 

b5 Boolean [CHANGE only] TRUE if at least one file was 

not changed because the destination file 

already existed 

A job that uses this new syntax will be aborted if it is run on a 

12.0 or earlier MCP. 

Example: 

BEGIN JOB DEMONSTRATE/CHANGE/AND/REMOVE; 

BOOLEAN BFAILED, BMISSING, BLOCKED, BSEC, BDUP; 

INTEGER COUNT; 

CHANGE CHANGETEST1/= TO CHANGETEST3/=, 

CHANGETEST5/= TO CHANGETEST2/=, 

CHANGETEST6 TO CHANGETEST7 

[BFAILED, COUNT, BMISSING, BLOCKED, BSEC, BDUP]; 

218 6875 9497–003


DISPLAY "Change test: " & STRING (COUNT, *) & " files changed"; 

IF NOT BFAILED THEN 

DISPLAY "All files changed"; 

IF BMISSING THEN 

DISPLAY "Missing files"; 

IF BLOCKED THEN 

DISPLAY "Locked files seen"; 

IF BSEC THEN 

DISPLAY "Security error seen"; 

IF BDUP THEN 

DISPLAY "Duplicate files seen"; 

REMOVE CHANGETEST3/=, 

CHANGETEST2/=, 

CHANGETEST7 

[BFAILED, COUNT, BMISSING, BLOCKED, BSEC]; 

DISPLAY "Remove test: " & STRING (COUNT, *) & " files removed"; 


DISPLAY "All files removed"; 





IF BSEC THEN 




CHANGETEST7 

[BFAILED, COUNT]; % Not all variables are needed 




END JOB 


Message RES12 Now Includes a File Name 

SYMPTOMS: 

When RESERVE issues the RSVP "WAITING FOR SEGMENTS" it is 

not clear what that message means or what file is blocking RESERVE 

from finishing. 


Make changes to the "System Message Support Reference Manual" as 

follows. 

6875 9497–003 219


Replace message RES1 "WAIT ON TEMPORARY FILE" with the following 

new message and explanation. 

PK COULD NOT RESERVE TEMPORARY FILE (RES1) 

Cause 

Execution of a RES (Reserve) system command was unable to reserve 

the indicated file because one or more processes are using the 

file. The RESERVE process continues with other files. 

Response 

Choose one of the following actions: 

.Wait for the RESERVE process to issue the RSVP message 

PK RESERVE INCOMPLETE: OK TO RETRY, QT FOR RES 

(RES12) 

.Use the SHOWOPEN system command to determine the process or 

processes that are using the file. 

.To terminate the RESERVE process and have it mark the currently 

reserved space as available, enter DS. 


reserved space as RESDISK, enter QT. 

Replace message RES2 "WAIT ON TEMPORARY FILE OWNED 

BY MIX" with the following new message and explanation. 

PK COULD NOT RESERVE TEMPORARY FILE 

OWNED BY MIX (RES2) 

Cause 

Execution of a RES (Reserve) system command was unable to reserve 

the indicated file because the indicated process is using the 

file. The RESERVE process continues with other files. 

Response 

Choose one of the following actions: 

.Wait for the RESERVE process to issue the RSVP message 

PK RESERVE INCOMPLETE: OK TO RETRY, QT FOR RES 

(RES12) 

.Use the SHOWOPEN system command to determine all the processes 

that are using the file. 


reserved space as available, enter DS. 

220 6875 9497–003



reserved space as RESDISK, enter QT. 

For message RES3 "WAITING FOR SEGMENTS", replace the 

message, and explanation with the following: 

PK SECTORS OUT OF SECTORS ARE STILL 

IN USE OR ARE NOT ACCOUNTED FOR.(RES3) 

Cause 

A RESERVE process was unable to reserve all the specified area 

because some of the area contained files that are in use by 

the system or other programs. 

Response 

Note the number of sectors that haven't been reserved (the first 

number in the message). If the RESERVE process retries the 

reserve and again issues this message, compare the new value to 

check if the RESERVE process has made any progress. 

Change the text of RES12 -- PK RESERVE INCOMPLETE: OK TO 

RETRY, QT FOR RESDISK, as follows. Add a to the end of 

the message: 

PK RESERVE INCOMPLETE: OK TO RETRY, QT FOR RESDISK 

(RES12) 

The variable is the FILENAME of the last file that 

blocked RESERVE from finishing. 

Make changes to the "Cause" and "Response" texts for message RES12, 

Add the following to the "Cause" as a second paragraph for RES12: 

After some interval the RESERVE process will cancel the RSVP 

and automatically start running again, trying to reserve any areas 

it has not already reserved. In some cases the RESERVE process is 

never able to complete because the remaining sectors are in use 

by another process or, in the case of a halt/load capable family, 

some areas set aside for use by the system can never be reserved. 

And replace the first paragraph of the "Response" for RES12, replace 

"Note the files ... following replies" with the following paragraph: 

Note the FILENAME in the RSVP message. Then either wait for the 

RESERVE process to cancel the RSVP and retry the reserve; or reply 

to the RSVP request by entering one of the following responses: 

6875 9497–003 221



Improve "FILE REMOVED" Messages 

SYMPTOMS: 

"FILE REMOVED" messages do not include a count of in use files 

that were removed. 


The file(s) REMOVED and file(s) REPLACED now include an "IN USE" 

term when a file or files that are in use are removed or replaced. 

The following is a list of the new messages and updated old 

messages: 

PK REMOVED ON (DIR4) 

PK REMOVED ON (IN USE)(DIR4) 

PK REMOVED FILES IN 

ON (DIR54) 

PK REMOVED FILES 

IN ON ( (IN USE) (DIR54) 

PK REPLACED ON (DIR85) 

PK REPLACED ON (IN 

USE)(DIR85) 

PK REMOVED WITH DESTROY OPTION ON 

(DIR106) 

PK REMOVED WITH DESTROY OPTION 

ON (IN USE)(DIR106) 

PK REMOVED WITH DESTROY OPTION FILES 

IN ON (DIR107) 

PK REMOVED WITH DESTROY OPTION FILES 

IN ON ( (IN USE)(DIR107) 



SYMPTOMS: 



222 6875 9497–003



to CDs. 










SYMPTOMS: 




to CDs. 









FILEDATA Reports PROTECTED File Attribute 


FILEDATA will report the PROTECTION = PROTECTED file attribute 

value for LFILES requests and ATTRIBUTES requests. 

For the LFILES and ATTRIBUTES cases, if you specify ALL or 

PROTECTION then FILEDATA will report the value of the PROTECTION 

attribute as PROTECTED or SAVE. 

6875 9497–003 223



NOLABEL Option for PG PK 


The NOLABEL option for the PG PK command adds the ability to remove 

the MCP label from a disk pack. 

The revised syntax for the PG PK is as follows: 

-- PK -- ----------------------------------> 

>-------------------------------------------------------------| 

| | 

| |

PG PK NOLABEL 


Erases the first 28 sectors of the disk specified in the unit 

number list with binary zeros. When ERASE is also specified, all 

but the first 28 sectors of the disk are erased using the algorithm 

specified. This is followed by the erasing the first 28 sectors 

using the algorithm specified. 


Fix Disk File Header Message 

SYMPTOMS: 

The segment number in the disk file header error message DIR121: 

PK ERROR WRITING SEGMENT AT OF 

HEADER BASED AT ON 

was incorrect for the first segment number. 


Make changes to the "System Message Support Reference Manual" 

as follows. 

For messages DIR121 and DIR122 replace the word "SEGMENT" in 

the text of these messages with "HEADER SEGMENT. 


Fix Disk File Header Message 

SYMPTOMS: 

The segment number in the disk file header error message DIR121: 

PK ERROR WRITING SEGMENT AT OF 

HEADER BASED AT ON 

was incorrect for the first segment number. 


Make changes to the "System Message Support Reference Manual" 

as follows. 

For messages DIR121 and DIR122 replace the word "SEGMENT" in 

the text of these messages with "HEADER SEGMENT. 

6875 9497–003 225



GETSTATUS Miscellaneous Subtype 21 May Hang System 

SYMPTOMS: 

If the array passed to GETSTATUS for a TYPE 2 (Miscellaneous 

REQUEST), Subtype 21 (SECOPT MECHANISMS) is too small then 

the system may eventually hang. 


In the "Security Administration Guide" there is a discrepancy in 

the syntax diagram for the metatoken 

for the SECOPT system command. Under the topic "Secopt Command" 

in the "MCP Security Policy Management" sub-sub-section of the 

"Controlling System Security Options" sub-section of the 

"Security Configuration" section it shows: 

 

--- MECHANISMS -----------------------------------------| 

The first rail of the diagram shows the letters "MECH" in bold. 

Replace that rail with the following rails: 

------ MECH ---------------------------------------| 

|--- MECHANISMS ---| 

without any bold letters. 


Halt Load May Hang Waiting for JOBDESC File 

SYMPTOMS: 

If the DL JOBS disk family has a duplicate SYSTEMDIRECTORY then 

the halt load process may hang with the RSVP: 

JOBDESC WAITING FOR [] 


Add a metatoken to the text of message RES5 as follows: 

PK ERROR RESERVING JOBDESC FILE: (RES5) 

is one of the following: 

TERMINATED BY 'QT' OR 'DS' 

226 6875 9497–003

BUFFER ALLOCATION ERROR 

BAD JOBDESC FILE 

NOT ENOUGH AVAILABLE DISK SPACE 

ERROR OPENING JOBDESC FILE 

ERROR CLOSING JOBDESC FILE 

READ I/O ERROR 

WRITE I/O ERROR 

IO ERROR 

Make changes for message RES4 as follows: 


Change the text from "... WAITING FOR JOB/SESSION ..." to: 

PK RESERVE BLOCKED BY JOB/SESSION 

(RES4) 

Where is QUEUED, RESTART, RUNNING, or WAITING TO PRINT 

Delete the second sentence under "Cause". Delete: 

The job might be queued for running or actually running. 

Delete message RES18: 

PK WAITING FOR JOB/SESSION (DONE) 


Halt Load May Hang Waiting for JOBDESC File 

SYMPTOMS: 

If the DL JOBS disk family has a duplicate SYSTEMDIRECTORY then 

the halt load process may hang with the RSVP: 

JOBDESC WAITING FOR [] 


Add a metatoken to the text of message RES5 as follows: 

PK ERROR RESERVING JOBDESC FILE: (RES5) 

is one of the following: 

TERMINATED BY 'QT' OR 'DS' 

BUFFER ALLOCATION ERROR 

BAD JOBDESC FILE 

NOT ENOUGH AVAILABLE DISK SPACE 

ERROR OPENING JOBDESC FILE 

ERROR CLOSING JOBDESC FILE 

READ I/O ERROR 

6875 9497–003 227


WRITE I/O ERROR 

IO ERROR 

Make changes for message RES4 as follows: 

Change the text from "... WAITING FOR JOB/SESSION ..." to: 

PK RESERVE BLOCKED BY JOB/SESSION 

(RES4) 

Where is QUEUED, RESTART, RUNNING, or WAITING TO PRINT 

Delete the second sentence under "Cause". Delete: 

The job might be queued for running or actually running. 

Delete message RES18: 

PK WAITING FOR JOB/SESSION (DONE) 


NOLABEL Option for PG PK 


The NOLABEL option for the PG PK command adds the ability to remove 

the MCP label from a disk pack. 

The revised syntax for the PG PK is as follows: 

-- PK -- ----------------------------------> 

>-------------------------------------------------------------| 

| | 

| |

| |- OWNER --------- ------------| | 

| | | | | | 

| | |- = -| | | 

| | | | 

| |- SERIAL --------- ----| | 

| | | | 

| |- = -| | 

| | 

| |












6 Unused 





Component: DMSII PRI-11582648 

DMS Logging 







occur. 


manual : 












230 6875 9497–003


6 Unused 






Fix DMSII Log Records 


SYMPTOMS: 

The length field in LINK words of Database Open, Close, Freeze and 

Resume log records is always zero. Loganalyzer output is not 

affected. 


In table 5-15 of the System Log Programming manual (86001807-217) 

add to the description of word 9 : 

Only occurs in open records where the program has specified an 

internal name - e.g. DATABASE MYDB = TESTDB. 


Fix DMSII Log Records 

SYMPTOMS: 

The length field in LINK words of Database Open, Close, Freeze and 

Resume log records is always zero. Loganalyzer output is not 

affected. 


In table 5-15 of the System Log Programming manual (86001807-217) 

add to the description of word 9 : 

Only occurs in open records where the program has specified an 

internal name - e.g. DATABASE MYDB = TESTDB. 

6875 9497–003 231


Component: GETSTATUS PRI-11418210 

Old Getstatus/Setstatus Mix Requests 


The Type 0 mix requests of both GETSTATUS and SETSTATUS have 

been deimplemented. 

In the Getstatus/Setstatus Manual (8600 0346-411) : 

Delete references to Type 0 from Section 1 - General Information 

on GETSTATUS and Section 8 - General Information on SETSTATUS. 

Delete Section 2 - GETSTATUS Request Type 0 (Mix Entry Calls) and 

Section 9 - SETSTATUS Request Type 0 (Mix Entry Calls). 

Component: GETSTATUS PRI-11560229 

GETSTATUS Miscellaneous Subtype 21 May Hang System 

SYMPTOMS: 

If the array passed to GETSTATUS for a TYPE 2 (Miscellaneous 

REQUEST), Subtype 21 (SECOPT MECHANISMS) is too small then 

the system may eventually hang. 


In the "Security Administration Guide" there is a discrepancy in 

the syntax diagram for the metatoken 

for the SECOPT system command. Under the topic "Secopt Command" 

in the "MCP Security Policy Management" sub-sub-section of the 

"Controlling System Security Options" sub-section of the 

"Security Configuration" section it shows: 

 

--- MECHANISMS -----------------------------------------| 

The first rail of the diagram shows the letters "MECH" in bold. 

Replace that rail with the following rails: 

------ MECH ---------------------------------------| 

|--- MECHANISMS ---| 

without any bold letters. 

232 6875 9497–003

Component: KEYS PRI-11474357 



SYMPTOMS: 






keys that are due to expire in the near future. The warning 

message is: 









specified: 


+---- - -----+ 



is a number between 0 and 127. Setting WARNFACTOR to 0 

disables the generation of warnings. 








Input 


6875 9497–003 233


Call 


TYPE 2 

SUBTYPE 111 



A [1] = 0 & 1 [38:06] 



to 30 days 


Results 


Example 


input: 

A [0] := 3; 

A [1] := 0 & 1 [38:06]; 

A [2] := 90; % Days 





includes: 




option 

0 = DONTCARE 

1 = NEVER 

2 = YES 





Operating System Information section of the Software 

Configuration (Type 17) call. 


234 6875 9497–003








and 






Cause 



Response 











Component: LIBMAINT PRI-11411240 

Improve NFT Messages 

SYMPTOMS: 

Often a "NETWORK" message issued by Library Maintenance for 

a DSSSUPPORT error does not have enough information to 

determine the cause of the problem. 


Make changes to the "System Support Messages Manual" as follows: 

In message LM71, change the word "network" to "NFT": 

6875 9497–003 235


'& BACKUP' IGNORED FOR NFT FILE TRANSFERS(LM71) 

Change the text for message LM75 from: 

to: 

HOST COPY TERMINATED BY NETWORK SIGNAL(LM75) 

NFT RETURNED A DS SIGNAL, HOST COPY TERMINATED(LM75) 

Change the text for message LM76 from: 

to: 

UNEXPECTED NETWORK SIGNAL= , ACTION= (LM76) 

UNEXPECTED NFT SIGNAL = ; REQUEST = 

: (LM76) 

Where is one of the following: 

NO MORE 

TERMINATE AND REMOVE NFTTEMP FILE 

SKIP FILE 

RECOPY 

COMPARE NOT ALLOWED 

COMPARE ALLOWED 

END OF FILE 

FILE NOT REQUIRED 

RESTART BLOCK 

TERMINATE BUT DO NOT REMOVE NFTTEMP FILE 

NETWORK I/O ERROR 

and where is one of the following: 

SAVE DIRECTORY 

REEL SWITCH 

GET TAPE DIRECTORY 

GET HEADER 

GET DATA 

SEND TAPE DIRECTORY 

SEND HEADER 

SEND DATA 

SEND DS SIGNAL 

SEND SKIP FILE SIGNAL 

SEND RECOPY SIGNAL 

SEND COMPARE NOT ALLOWED SIGNAL 

SEND COMPARE ALLOWED SIGNAL 

SEND END OF FILE SIGNAL 

SEND FILE NOT REQUIRED SIGNAL 

SEND RESTART BLOCK SIGNAL 

236 6875 9497–003


Warning 186 for Task Attributes SW6 and SW7 



On software released after 12/2010 Library Maintenance 

will no longer use task attributes SW6 or SW7 to determine 

the disk file header level to write to tapes. 

Add the following new messages to the "System Messages Support 

Reference Manual". 

Warning 186: Library Maintenance will no longer use the task 

attributes SW6 or SW7 to determine the disk file header level to 

write to tape in software released after 12/2010. (WARNG186) 

You specified the task attribute SW6 = TRUE or the task 

attribute SW7 = TRUE. 

Delete these settings from your COPY and ARCHIVE job files. 

MT LOCATE-POSITION FOR FAILED 

(LM297) 

The variable is one of the following: 

COMPARE DIRECTORY 

COMPARE FILE 

RETRY COPY 

MARK FILE MISSING 

An I/O error occurred when Library Maintenance tried to 

reposition the tape with a Fast Locate IOCW. Library 

Maintenance terminates without copying any more files. 

Check for preceding tape I/O error messages. 

MT TAPE POSITIONING ERROR DOING SPACE 

WHILE : (LM298) 


FORWARDS 

BACKWARDS 


COMPARING DIRECTORY 

OPENING DESTINATIONS 

SEARCHING FOR FILES IN DIRECTORY 

WRITING DIRECTORY 

BACKSPACING TAPES 

6875 9497–003 237


COMPARING DIRECTORY 

SEARCHING FOR NEXT FILE TO COPY 

COPYING 

COMPARING 

VERIFYING 

Make changes to the text and explanations of the following 

messages. 

For message LM36, replace the current message test: 

LIST OF FILE NAMES GREATER THAN ONE MILLION WORDS LONG(LM36) 

and explanation with the following new message and explanation: 

MT ERROR REWINDING TAPE : (LM36) 

For a COPY & VERIFY to tape process, Library Maintenance 

detected an error when it tried to rewind the tape to begin 

the Verify phase. Library Maintenance tries to continue with 

the verify. 

Check for a preceding tape I/O error messages. If Library 

Maintenance fails or gets verify errors, decide if you should 

re-submit the copy statement. Make sure you do not make the 

tape unit not-ready when Library Maintenance rewinds it to 

do the verify. 

For message LM27, change the message text to include the "phase": 

MT BACKSPACE TO FAILED TO REACH A TAPEMARK 

(LM27) 

and also for message LM27 add: 


COMPARE DIRECTORY 

COMPARE FILE 

RETRY COPY 

MARK FILE MISSING 

For message MISC41, change the message text to read as follows: 

FAULT : (MISC41) 

and also for message MISC41 add: 


DIVIDE BY ZERO 

EXPONENT OVERFLOW 

238 6875 9497–003

EXPONENT UNDERFLOW 

INVALID INDEX 

INTEGER OVERFLOW 

INVALID OPERAND 

INVALID ADDRESS 

STRING PROTECT 

 


Minor Improvements to NFT 



Make changes to the "Distributed System Services Operations Guide" 

as follows. 

Under "Sources of information on Installing DSS Providers" in the 

"Installing DSSs" section, make the following changes. 

Add the following notes to the first bullet item -- "You install 

Host Services and NFT ...": 

Note: If the release level of the DSSSUPPORT library is not the 

same as the release level of the MCP then the NFT restart or 

resume function may not work correctly. 

Note: The 54.1 DSSSUPPORT uses a new version (541) for 

FTRECOVERY files instead of the old version (1). If you attempt 

to do an NFT Restart on a level 54.1 or newer level system with 

an FTRECOVERY file generated by a 53.1 or older level system, NFT 

will re-copy all the files from the start. If you attempt to do 

an NFT Restart on a level 53.1 or older level system with an 

FTRECOVERY file generated by a 54.1 or newer level system, NFT 

will re-copy all the files from the start. 

In the "Native File Transfer (NFT)" section make the following 

changes. 

Add the following new bullet item to the first "paragraph": 

.File transfers from Library Maintenance CDs 

Change the name of the "Using WFL Commands to Run NFT" subsection 

to: 

Using WFL Statements to Run NFT 

Change the fourth bullet item under "Explanation" in this 

sub-section as follows -- add CDs: 

If you use tapes or CDs as sources, you must specify a single 

destination volume. 

6875 9497–003 239



Improve Library/Maintenance Error Message 


Make changes to the "System Messages Support Reference Manual", 

(86000429-610) : 

Replace the text of message LM96: 

MT INVALID LIBRARY/MAINT TAPE BLOCKSIZE, DEFAULT 

ASSUMED(LM96) 

with: 

MT INVALID LIBRARY MAINTENANCE TAPE BLOCKSIZE 

, DEFAULT BLOCKSIZE ASSUMED(LM96) 

Under "Cause" for this message, in the second bullet item, 

change "... file header 2 (HDR2 label) ..." with: 

... file header 2 (HDR2 label) or file header 3 (HDR3 label) ... 


Generate Warning When File Marked Restricted During UNWRAP 

SYMPTOMS: 

Files can be inadvertently left restricted after an UNWRAP 

operation. 


A message is now generated when a user who has sufficient privilege 

to mark hazardous files as not restricted unwraps hazardous files 

and leaves them restricted. 

Add the following message to the System Messages Support Reference 

Manual (form # 8600 0429). 

Some files were marked as RESTRICTED = TRUE. (LM299) 

Cause 

An UNWRAP operation unwrapped at least one hazardous file which was 

marked restricted. The UNWRAP operation was performed by a user 

with sufficient privilege to mark the files as not restricted. 

240 6875 9497–003

Response 


Determine whether any files need to be unrestricted. Use the 

RESTRICT - FILE system command to mark those files as not 

restricted. 

You can prevent files from being restricted using one of the 

following two methods. You should ensure that it is safe to 

do so. 

o Specify a TO clause with the attribute (RESTRICTED = FALSE) 

when unwrapping files 

o Reset the security option RESTRICTUNWRAP (SECOPT- 

RESTRICTUNWRAP). 

Note that resetting the option will reduce the security of your 

system, allowing non-privileged users to unwrap and execute code 

files 

If you wish to continue unwrapping files as restricted files, and 

do not wish to see this message, set the SW8 attribute to TRUE for 

the UNWRAP statement. 

Add the following information to the Work Flow Language (WFL) 


Add these sentences at the end of the paragraph starting "The 

unwrap process re-creates ..." in the UNWRAP Statement topic of 

the Statements section: 

When a file is marked restricted and the user has sufficient 

privilege to remove the restriction, a message indicating that 

files have been restricted is generated. This message can be 

suppressed by setting the task attribute SW8 to TRUE in the 

UNWRAP statement. 


Correct Description of Libmaint Tapes 


Make changes to the "Format of Library Maintenance Tapes" appendix 

in the "I/O Subsystem Programming Reference Guide" as follows. 

Under "Format of Library Maintenance Tapes with Standard Labels", 

replace the paragraph that says "First copied file ... might be 

shorter." with: 

First file copied. The first word of each block contains the 

block number, starting at 1. The first block or blocks contain 

6875 9497–003 241


the disk file header. If bit [47:1] of the first word of the 

first block is equal to 1 then the file was not copied to the 

tape. Otherwise the first block contains the first or only 

segment of the disk file header. The maximum size of the disk 

file header blocks is 2048 words. The number of blocks needed 

for the disk file header is determined by the length of the 

disk file header in words. The length of the disk file header is 

stored in word 3 field [15:16] of the first block of the header. 

If the file is not an empty file, then Library Maintenance 

copies the data blocks to the tape after it finishes copying 

the disk file header to the tape. The maximum size of each data 

block is determined by the tape BLOCKSIZE, which is stored in 

the HDR2 label of the first file on the tape. For tapes with 

standard labels Library Maintenance aligns each record of 

900 words or less on a 900 word boundary in the block. 

Library Maintenance writes data blocks shorter than the tape 

BLOCKSIZE when the length of the last record in a block is less 

than the Library Maintenance record size. This can happen in 

cases where the tape BLOCKSIZE does not divide evenly into the 

disk files AREASECTORS value multiplied by 30 words per sector. 

The last data block is often shorter than the tape BLOCKSIZE 

because of the value of the LASTRECORD attribute of the 

disk file. 

Under "Format of Library Maintenance Tapes in Compact Form", 

replace the paragraph that says "First copied file ... HDR2 label 

for FILE001." with: 

First file copied. The first word of each block contains the 

block number, starting at 1. The first block or blocks contain 

the disk file header. If bit [47:1] of the first word of the 

first block is equal to 1 then the file was not copied to the 

tape. Otherwise the first block contains the first or only 

segment of the disk file header. The maximum size of the disk 

file header blocks is 2048 words. The number of blocks needed 

for the disk file header is determined by the length of the 

disk file header in words. The length of the disk file header is 

stored in word 3 field [15:16] of the first block of the header. 

If the file is not an empty file, then Library Maintenance copies 

the data blocks to the tape after it finishes copying the disk 

file header to the tape. The maximum size of each data block is 

determined by the tape BLOCKSIZE, which is stored in the HDR2 

label of the first file on the tape. For tapes in compact format 

Library Maintenance puts each 30 to 900 word record into the 

block immediately after the end of the previous record. Some or 

all of the data blocks might be shorter than the tape BLOCKSIZE 

if the tape BLOCKSIZE does not divide evenly into the disk files 

AREASECTORS value multiplied by 30 words per sector. The last 

data block is often shorter than the tape BLOCKSIZE because of 

the value of the LASTRECORD attribute of the disk file. 

Under "Format of Tape Directory", delete the one sentence 

242 6875 9497–003


paragraph "The link information ... as follows", 

delete the CHARCNT and SKIPF fields that follow that paragraph, 

and delete the next paragraph "CHARCNT and SKIPF are needed ... 

to this volume". 


Locking KEYEDIOII Files 

SYMPTOMS: 

When Library Maintenance copies a KEYEDIOII file from disk it 

locks all the physical files making up that KEYEDIOII file. 

Library Maintenance does not unlock them until it has copied all 

the files specified in the copy statement. 


When Library Maintenance copies a KEYEDIOII file from disk it 

locks all of the physical files making up that KEYEDIOII file. 

Library Maintenance now unlocks the KEYEDIOII physical files making 

up the KEYEDIOII file when it finishes copying files from that 

source. That is, Library Maintenance unlocks the KEYEDIOII files 

when it finishes copying the files under that FROM clause. 

Component: LIBRARIES PRI-11480993 

Implement LI ODT Command 

SYMPTOMS: 

It is difficult to determine the libraries that a task is linked to. 


The LI ODT command reports information about libraries that a 

task is linked to. 

In the System Commands Manual (3826 5419-000) add this description 

for the LI command : 

LI (Library Information) 

The LI (Library Information) command reports information about 

libraries that the specified tasks are linked to. 

Syntax 

----LI------------------ 

6875 9497–003 243


Explanation 


and task name of the libraries to which the tasks in the 

are linked. "CL" denotes a connection 

library and "SL" denotes a server library. 

Example 

2188 LI 


Type Job Task 





library. 

In the CANDE Operations Manual (8600 1500-505) add this description 

for the LI control command : 

?LI 

Syntax 

--?--------------------LI------------------ 

| | 

|--| 

Explanation 

The ?LI command reports information about libraries to which 

the specified task is linked. If a is not 

specified, the command reports information on the program 

currently running. 


and task name of the libraries to which the task is linked. 

"CL" denotes a connection library and "SL" denotes a server 

library. 

Example 

?LI 


Type Job Task 





library. 

244 6875 9497–003


In Section 7 (Getstatus Type 6) of the GETSTATUS/SETSTATUS manual 

(8600 0346-412) add this description for SUBTYPE 18 calls : 

SUBTYPE 18 Calls (Library Information) 

For SUBTYPE 18, GETSTATUS reports library information for a list of 

mix numbers. 

Input 

The caller should set up the array ARY as follows: 

Word Field Description 

ARY [0] [19:20] index to the result area. The area between 

ARY [1] and the result area contains mix number 

request groups. This area must contain an even 

number of words; otherwise, hard error 34 is 

returned. 

ARY [1] through Mix number request groups. 

ARY [ARY [0]-1] 

The format of a mix number request group is as follows: 


ARY [n] 0 

ARY [n+1] GS_TASKNO_F [39:40] Mix number of the process to report 

The SUBCLASS parameter determines how an out-of-space condition is 

handled. Set bit 37 of the SUBCLASS parameter if you want GETSTATUS 

to return partial library information when the array parameter 

is not large enough to contain all the requested information for 

a mix number. 

Results Returned 


ARY [n] GSERRORF [47:01] 1 = There was an error obtaining 


GSADDLINFOF [46:08] If ARY[n].[47:01] = 1 then this 

field contains the error value 

associated with trying to obtain the 


GS_INDEX_F [19:20] The word index to where the 

information for this mix starts. 

ARY [n+1] GS_TASKNO_F [39:40] Mix number of the process. 

6875 9497–003 245


GETSTATUS replaces ARY [n].[19:20] of each mix number entry with a 

link pointing to a structure containing links to library 

information for that mix number. The link value is 0 if no 

libraries are found for that mix number. 

If GETSTATUS finds linked libraries for a given mix number, the 

value in ARY [n].[19:20] is the index of the word in the ARY array 

parameter of the library link structure for that mix number. The 

first word in the library link structure is the number of linked 

libraries. For each library there is a link word pointing to a 

library information structure. 

The library information structure is 2 to 4 words long, depending 

on the bits in the MASK parameter. The first word (word 0) is a 

validity mask. (See Table 7-nn for details of the items addressed 

by each MASK bit.) If a validity mask bit is on, then the 

corresponding library information structure word is valid. 

(See Figure 7-nn for details.) All of the values are returned 

as single words, except the task name, which is a word offset 

from the library link structure into the array of the task's 

name in standard form. 

If an error occurs, such as an invalid mix number, then the soft 

error result is returned as follows. ARY [n].[47:01] of the mix 

number entry is set to 1. ARY [n].46:08] of the mix number entry 

contains the number of the soft error. 

If there is not enough room in the array for all the information 

requested, GETSTATUS sets bit [47:01] of word 0 of the array 

parameter to 1. If an out-of-space condition occurs while adding 

specific file information and bit 37 of the SUBCLASS parameter is 

set to 1, the mask word in the file information structure for all 

subsequent files is 0. If bit 37 of the SUBCLASS parameter is set 

to 0, and the out-of-space condition occurs, no information is 

returned for mix number. You should make another call with a larger 

array or with fewer mix numbers. If the array is already of 

maximum size, and the out-of-space condition occurs for the first 

mix number, you should make another call with bit 37 of the 

SUBCLASS parameter set to 1. 

Mix number structure 

|count of mix|link/mix |......|link/mix |link/mix | 

|numbers *2 |number group|......|number group|number group| 

| |number 1 |......|number n-1 |number n | 

Library link structure 

|count of |library|.........|library|library| 

|libraries|link |.........|link |link | 

Library information structure 

X X+1 X+2 X+3 

|Validity|Task |Job |Mix | 

|mask |name |number|number| 

246 6875 9497–003

Figure 7-nn Mix Number Links 


Table 7-nn Corresponding Library Information For Each Mix Number 

Mask bit Name Description 

0 TASKNAME Link to the library name 

1 JOBNUMBER Job number of the library 

2 MIXNUMBER Mix number of the library 

Component: LOGGING PRI-11487581 

LOGGING MINIMAL and LOGGING DEFAULT Values 


GETSTATUS type 2 (Miscellaneous Request), subtype 76 (LOGGING) can 

now return default LOGGING information for the DEFAULT (*) and 

MINIMAL settings. 

If SUBCLASS is 3, the array is filled with LOGGING DEFAULT values. 

If SUBCLASS is 4, the array is filled with LOGGING MINIMAL values. 














form) 





6875 9497–003 247
















form) 











written. 






248 6875 9497–003








|-- /1\ -- RBAC ---| 











|-- /1\ -- RBAC ---| 


RBAC 




follows. 










the name. 

6875 9497–003 249













5 ADD_ROLE 

6 DELETE_ROLE 


















250 6875 9497–003










Minor 





All Logging is in Version 1 Format 


The system no longer creates version 0 SYSTEM/SUMLOG entries. 

All entries in the SUMLOG are in version 1 format. 


All Logging is in Version 1 Format 


The system no longer creates version 0 SYSTEM/SUMLOG entries. 

All entries in the SUMLOG are in version 1 format. 

Component: LOGICALIO PRI-11469001 


SYMPTOMS: 




6875 9497–003 251






























Improve Tape Error Messages 

SYMPTOMS: 

When the system tries to ready a tape unit and an error occurs, 

the system marks the tape as UNLABELED without giving any 

explanation of what went wrong. 

252 6875 9497–003



Make changes to the "System Messages Support Reference Manual". 

Under "Metatokens in Messages" in Section 1 "Locating and Reading 

System Messages" add the following tokens and definitions: 

A hexadecimal display of binary data. 

The LINENUMBER in the MCP where an error 

occurred. 

Add the following new messages and explanations to the "System 

Messages Support Reference Manual": 

MT [] INVALID EXTMODE 

4'' IN CHARACTER 19 OF ANSI69 HDR2 LABEL(DPC98) 

Cause 

While readying the tape or trying to open a file on the 

tape the system found the indicated invalid character in the 

EXTMODE field of the HDR2 label. The system sets the EXTMODE 

file attribute value to EBCDIC. 

Response 

Notify programmer. This discrepancy may cause the program to 

read data from the tape incorrectly. 

MT [] ERROR READING LABEL, 

LRD= @ (DPC101) 

Where is VOLn, UHLn, or HDRn. 

Cause 

While readying the tape or trying to open a file on the tape the 

system got an I/O error while trying to read the indicated label. 

The system marks the tape as UNLABELED. 

Response 

If the tape is not still in use, try and move the tape volume 

to another tape unit to see if the problem was caused by 

the unit or the data on the volume. 

MT [] EXPECTED VOL1 LABEL, FOUND BLANK 

TAPE @ (DPC102) 

Cause 


system got an I/O error while trying to read the VOL1 

label. The system marks the tape UNLABELED. 

Response 




6875 9497–003 253


MT [] EXPECTED LABEL BUT FOUND 

4'' @ (DPC220) 

Cause 


system found a label id that was invalid or out-of-sequence. 


Response 




MT [] ERROR TRYING TO SET/RESET 

COMPRESSION @ (DPC260) 

Cause 


system got an error trying to set or reset the compression 

of the unit to match the compression that the tape was written 

with. The system marks the tape as UNLABELED. 

Response 




MT [] ERROR REWINDING TAPE, LRD= 

@ (DPC261) 

Cause 

While readying the tape the system got an I/O error trying to 

rewind the tape. The system marks the tape as UNLABELED. 

Response 




MT [] ERROR SPACING TAPE BACKWARDS, 

LRD= @ (DPC262) 

Cause 


system got an I/O error trying to backspace the tape. The system 

marks the tape as UNLABELED. 

Response 




MT [] EXPECTED '65' IN CHARACTERS 29-30 

OF VOL1 LABEL, BUT FOUND 4'' 

254 6875 9497–003

@ (DPC263) 


Cause 


system found invalid information in the ASCI69 VOL1 label for 

the tape. The system marks the tape as UNLABELED. 

Response 




MT EXPECTED FILENAME IN CHARACTERS 18-23 OF 

B3500STANDARD 'LABEL', FOUND 4'' @ (DPC264) 

Cause 


system found invalid information in the LABEL of a B3500STANDARD 

the tape. The system marks the tape as UNLABELED. 

Response 




MT [] EXPECTED A '4' IN CHARACTER 80 OF 

ANSI87 VOL1 LABEL, BUT FOUND 4'' @ (DPC265) 

Cause 


system found invalid information in the ANSI87 VOL1 label of the 

tape. The system marks the tape as UNLABELED. 

Response 




MT [] WARNING: SCRATCH TAPE -- UNIT NOT 

WRITE-ENABLED @ (DPC266) 

Cause 

While readying the tape the system found that it is a scratch 

tape, but the tape unit is not write-enabled. 

Response 

To make the scratch tape available for use, 

write-enable the tape unit. Use the "MODE MT IO" 

system command. Then use the "RY MT" system 

command. 

MT [] DID NOT FIND TWO TAPE MARKS AFTER 

ANSI87 VOL2 LABEL OF SCRATCH TAPE @ (DPC267) 

Cause 

6875 9497–003 255


While readying the tape the system found that it appears to be 

a scratch tape, but the double tape marks at the end of the 

labels are missing. 

Response 

Decide if you should use the "PG MT " system 

to mark the tape as a scratch tape. 

MT [] INVALID EXTMODE 4'' 

IN CHARACTERS 5-9 OF ANSI87 HDR3 LABEL(DPC268) 

Cause 

While readying tape volume or opening a tape file the system 

found the indicated invalid character in the EXTMODE field 

in the HDR3 label. The system sets the EXTMODE file 

attribute value to EBCDIC. 

Response 

Notify programmer. This discrepancy may cause the program to 

read data from the tape incorrectly. 

MT EXPECTED A '0' OR 'E' IN CHARACTER 11 OF ANSI87 

VOL1 LABEL FOR A SCRATCH TAPE, BUT FOUND 4'' 

@ (DPC269) 

Cause 


an ANSI87 scratch tape, but the scratch tape code in the VOL1 

label is not correct. The system will mark the tape as 

UNLABELED. 

Response 

Use the "PG MT " system command to mark the tape 

as a scratch tape. 

MT EXPECTED A '0' IN CHARACTER 31 OF ANSI87 VOL2 

LABEL FOR A SCRATCH TAPE, BUT FOUND 4' 

@ (DPC270) 

Cause 


an ANSI87 scratch tape, but the TAPE TYPE code in the VOL2 

label is not correct. The system marks the tape as 

UNLABELED. 

Response 

Decide if you should use the "PG MT " system command 

to mark the tape as a scratch tape. 

MT [] INVALID LABELKIND 

IN UINFO @ (DPC271) 

Cause 

While trying to open a file on a tape the system found an invalid 

256 6875 9497–003


value for the LABELKIND file attribute in the MCP internal UINFO 

table. The system marks the tape as UNLABELED. 

Response 

Notify a UNISYS system engineer. 


Error Messages for READALABEL 


Make changes to the "System Messages Support Reference Manual". 

For message LM44, change "TAPEMARK" to "TAPE MARK". 

Add the following new messages and explanations. 

MT 'DISPLAYTOSTANDARD' RETURNED 

ERROR FOR GUARDFILETITLE IN ANSI87 'VOL3' LABEL(DPC272) 

Cause 

While readying the tape the DISPLAYTOSTANDARD procedure 

returned the indicated error while trying to translate the 

GUARDFILETITLE from display form to standard form. 


Response 

Determine who created the tape and notify them of the problem. 

MT 'DISPLAYTOSTANDARD' RETURNED ERROR 

FOR LIBMAINTDIR FILE NAME IN ANSI87 'VOL5' LABEL(DPC273) 

Cause 

While readying the tape the DISPLAYTOSTANDARD procedure 

returned the indicated error while trying to translate the 

FILENAME from display form to standard form. The system 


Response 


MT EXPECTED 'MCP/AS' IN CHARACTERS 

25-30 OF ANSI87 VOL1 LABEL FOR A CONDITIONED LIBRARY/MAINTENANCE 

TAPE, BUT FOUND 4'' @ " (DPC274) 

Cause 

While readying the tape the system found the wrong code in the 

implementation identifier field of the VOL1 label. The system 


6875 9497–003 257


Response 


MT EXPECTED LABELLEVEL GEQ 04 IN 

CHARACTERS 31-32 OF ANSI87 VOL1 LABEL, BUT FOUND 4'


The following diagram shows the layout of the information in 

the array that SYSTEMSTATUS returns: 

----------- 

| GS Word | 

----------- 

----------- 

| GS Word | 

----------- 

----------- ---------------------------- 

| GS Word | | Major # | Info for Major | 

----------- ---------------------------- 

----------- ---------------------------- 

| GS Word | | Minor # | Info for Minor | 

----------- ---------------------------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- 

| GS Word | 

----------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- ---------------------------- 


----------- ---------------------------- 

The first group size (GS) word specifies the entire length 

of all the information returned. 

Following this are major type group entries. The first group- 

size word specifies the length of the major type group entry, 

the second group-size word specifies the length of the 

description information. 

Following the major type description are minor type group 

entries. The group-size word specifies the length of the 


Note that for V1 subtype 1, no minor type group entries are 

included. 

Major Type Information 

Word Type Name and Meaning 

0 I Group-size word 

This value indicates the number of words 

occupied by the major type information. The 

primary purpose of this value is to allow 

6875 9497–003 259


1 Major type number 

convenient indexing to beginning of the 

minor type information 

2 Reserved for expansion 


4 I Size of major type description (in words) 

5 S Major type description (null terminated) 

Minor Type Information 



1 Minor type number 


occupied by the minor type information. The 


convenient indexing to subsequent entries 



4 I Size of minor type description (in words) 

5 S Minor type description (null terminated) 

Component: LOGTABLEGEN PRI-11545939 

Retrieve Log Descriptions 


A new SYSTEMSTATUS call can be used to retrieve log descriptions. 

The descriptions include the name of the major and minor types. 

The new call is defined as follows: 

Logging Descriptions (Type 6) 

SYSTEMSTATUS type 6 returns log descriptions for major and 

minor types. SYSTEMSTATUS uses the V1 and V2 parameters to 

determine the information returned. 

For V1 subtype 0, SYSTEMSTATUS returns all major/minor type 

260 6875 9497–003

descriptions. 


For V1 subtype 1, SYSTEMSTATUS returns all major type 

descriptions. 

For V1 subtype 2, SYSTEMSTATUS returns descriptions for a 

specific major type. The major type is specified in V2.[47:24]. 


specific major/minor type. The major type is specified in 

V2.[47:24]. The minor type is specified in V2.[23:24]. 

If V1 subtype is 2 or 3 and the major type is larger than the 

maximum major type, error 36 (INVALIDSUBTYPE) is returned. If 

V1 subtype is 3 and the minor type is larger than the maximum 

minor type for the specified major type, error 36 

(INVALIDSUBTYPE) is returned. 

Response Format 



----------- 

| GS Word | 

----------- 

----------- 

| GS Word | 

----------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- 

| GS Word | 

----------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- ---------------------------- 


----------- ---------------------------- 




6875 9497–003 261









included. 


























262 6875 9497–003

Component: MAINTENANCE PRI-11485201 


Cannot Reinitialize MCPESRSUPPORT Library Without Halt/Load 

SYMPTOMS: 

If a new MCPESRSUPPORT library (*SYSTEM/ESRLOGGER) is installed, 

a halt/load is required before it can be used. 

If the MCPESRSUPPORT library is DSed, ESRs can no longer be sent. 


When the MCPESRSUPPORT function is established (with the system 

command SL MCPESRSUPPORT = ) and the library is running, 

the operator can now restart MCPESRSUPPORT. 

Add the following message to the System Messages Support Reference 

manual (form # 8600 0429): 

MCPESRSUPPORT function replaced; do you want to restart 

ESRLOGGER? (ESR5) 

Cause 

An SL MCPESRSUPPORT system command has established a new code 

file for the MCPESRSUPPORT function, and ESRLOGGER is already 

running as a library. 

Response 

Determine whether you want to use the new library immediately. 

If so, respond OK. The existing library will be terminated and 

the next time an ESR is generated, the new library will be used. 

If not, respond DS. The new library will not be used until the 

next halt/load. 

Note that if you respond DS and wish to use the new library 

without halt/loading, you should SL - MCPESRSUPPORT and resubmit 

the original SL command. 

Component: MEMORYMGMT PRI-11563775 

Memory Pools D-Note For CU System Command 


In the System Command Reference Manual (3826 5419-000) please 

make the following changes: 

Section 1. Commands 

6875 9497–003 263


CU (Core Usage) 

o Add CU POOLS and CU AVAIL POOLS to the Syntax diagram. 

CU ---------------------------------| 

| | | | | 

|-- AVAIL --| |-- POOLS --| | 

| | 

|--- OLAYLISTS ---| 

| | 

|--- SAVELISTS ---| 

| | 

|--- LISTS -------| 

o In the CU AVAIL explanation, add the following 

The Available Areas number represents the number of linked areas 

in save and non save lists. This value represents the number of 

available areas that constitute the Save and Non Save Avail Mem 

Totals. This number gives some indication of the amount of 

checkerboarding that is present in memory. The higher this 

number is, the greater the number is of available areas 

interspersed among inuse areas. 

The Not Linked Areas number represents the number of areas that 

are not linked in save or nonsave lists, and corresponds to the 

word value of Not Linked Avail Mem Totals. These are areas that 

are too small to hold inuse memory due to link requirements, and 

will only be reclaimed when an adjacent inuse area is deallocated 

or moved. 

o In the CU AVAIL LISTS, OLAYLISTS and SAVELISTS explanation, 

replace all references to the term "space" with the term "area". 

This is consistent with the use of area in the CU AVAIL display. 

o Add CU POOLS explanation as follows: 

Memory Pool areas contain individual ASD segments referred to as 

"pool objects". Each pool area is divided into a number of fixed 

size areas allowing allocation of a range of values. Pool areas 

are also subdivided into Save and Non Save Pool areas. The CU 

POOLS command displays the CU output followed by the memory 

statistics for all allocated Memory Pool areas, under the heading 

"Memory Pools Summary". This area is further divided into the 

following two headings. 

Memory Summary 

The Memory Summary area of the display shows total values of 

Available and In Use areas. The In Use values are further 

subdivided into Non Save and Save values, as well as pool object 

fragments and pool area not linked. The fragments represent the 

portion of the pool object that exceeds the segment requirement 

of the object. For example, if the pool area contains all 

objects from 8 to 15 words, and the actual segment requirement is 

264 6875 9497–003


10 words, the fragment is incremented by 5 words. The Not Linked 

value represents the total overhead of pool area management 

regions. 

Non Save and Save Pools 

The remainder of the display splits the memory statistics into 

Non Save and Save pool area summaries. The left column of each 

of the first three rows of the display shows the number of 

objects Available and Inuse and their Totals. The right side 

portion of these three rows shows the core value in words 

represented by these object counts and the corresponding total. 

For the fragment row, each left side shows the percentage of 

inuse pool object memory while the right side number is the value 

in words of pool object fragments. The not linked rows show the 

percentage value of pool area memory and the corresponding number 

of words of pool area not linked memory. Finally, the Areas row 

displays the number of Non Save and Save pool areas and their 

corresponding word requirements. 

o Add CU AVAIL POOLS explanation as follows: 

CU AVAIL POOLS display the Memory Pools Summary as described 

for CU POOLS, but below the CU AVAIL output instead of the CU 

display. 

o For examples 3, 4, 5 and 6, replace the term "Avail Mem Totals" 

contents with the following: 

------ Avail Mem Totals ----- 

Non Save 156,754,772 

Save 166,913,864 

Not Linked 278,845 

Available Areas 4,227 

Not Linked Areas 99,587 

"--- Maximum Size -- --- Minimum Size -- --- Total Areas -- " 

o For examples 4, 5 and 6, replace the term "Spaces" with "Areas" 

in the heading as follows: 


"--- Total Words --" 

o Add CU AVAIL POOLS example 7 as follows: 

----------------------------- SYSTEM MEMORY USAGE - ... 

----- Memory Summary ---- --- ASD Information -- 

Available 440,930,713 Available 2,343,478 

Non save 47,204,160 In use 398,548 

Save 57,124,647 Maximum 408,283 

Total 545,259,520 Total 2,742,026 

Overlaid 0 In use 15% : Max 15% 

6875 9497–003 265


... ----------------------------- 


Non Save 421,388,917 

Save 317,350,749 




---------------------------- Memory Pools Summary ------- ... 

----- Memory Summary ---- ------------ Non Save Pools -- 

Available 520,720 Avail 1,270 211,632 

Non save 18,970,444 In use 224,594 18,970,444 

Save 4,565,468 Total 225,864 19,182,076 

Fragments 931,608 Fragments 3.25% 637,828 

Notlinked 451,560 Notlinked 1.86% 376,516 

Total 25,439,800 Areas 2,469 20,196,420 

Component: MEMORYMGMT PRI-11564771 

... ----------------------- 

------- Save Pools ---- 

3,507 309,088 

65,290 4,565,468 

68,797 4,874,556 

6.05% 293,780 

1.43% 75,044 

641 5,462,116 

Memory Pools D-Note For CU System Command 


In the System Command Reference Manual (3826 5419-000) please make 

the following changes: 

Section 1. Commands 

CU (Core Usage) 

o Add CU POOLS and CU AVAIL POOLS to the Syntax diagram. 

CU ---------------------------------| 

| | | | | 

|-- AVAIL --| |-- POOLS --| | 

| | 

|--- OLAYLISTS ---| 

| | 

|--- SAVELISTS ---| 

| | 

|--- LISTS -------| 

o In the CU AVAIL explanation, add the following 

266 6875 9497–003


The Available Areas number represents the number of linked areas 

in save and non save lists. This value represents the number of 

available areas that constitute the Save and Non Save Avail Mem 

Totals. This number gives some indication of the amount of 

checkerboarding that is present in memory. The higher this 

number is, the greater the number is of available areas 

interspersed among inuse areas. 

The Not Linked Areas number represents the number of areas that 

are not linked in save or nonsave lists, and corresponds to the 

word value of Not Linked Avail Mem Totals. These are areas that 

are too small to hold inuse memory due to link requirements, and 

will only be reclaimed when an adjacent inuse area is deallocated 

or moved. 

o In the CU AVAIL LISTS, OLAYLISTS and SAVELISTS explanation, 

replace all references to the term "space" with the term "area". 

This is consistent with the use of area in the CU AVAIL display. 

o Add CU POOLS explanation as follows: 

Memory Pool areas contain individual ASD segments referred to as 

"pool objects". Each pool area is divided into a number of fixed 

size areas allowing allocation of a range of values. Pool areas 

are also subdivided into Save and Non Save Pool areas. The CU 

POOLS command displays the CU output followed by the memory 

statistics for all allocated Memory Pool areas, under the heading 

"Memory Pools Summary". This area is further divided into the 

following two headings. 

Memory Summary 

The Memory Summary area of the display shows total values of 

Available and In Use areas. The In Use values are further 

subdivided into Non Save and Save values, as well as pool object 

fragments and pool area not linked. The fragments represent the 

portion of the pool object that exceeds the segment requirement 

of the object. For example, if the pool area contains all 

objects from 8 to 15 words, and the actual segment requirement is 

10 words, the fragment is incremented by 5 words. The Not Linked 

value represents the total overhead of pool area management 

regions. 

Non Save and Save Pools 

The remainder of the display splits the memory statistics into 

Non Save and Save pool area summaries. The left column of each 

of the first three rows of the display shows the number of 

objects Available and Inuse and their Totals. The right side 

portion of these three rows shows the core value in words 

represented by these object counts and the corresponding total. 

For the fragment row, each left side shows the percentage of 

inuse pool object memory while the right side number is the value 

in words of pool object fragments. The not linked rows show the 

6875 9497–003 267


percentage value of pool area memory and the corresponding number 

of words of pool area not linked memory. Finally, the Areas row 

displays the number of Non Save and Save pool areas and their 

corresponding word requirements. 

o Add CU AVAIL POOLS explanation as follows: 

CU AVAIL POOLS display the Memory Pools Summary as described 

for CU POOLS, but below the CU AVAIL output instead of the CU 

display. 

o For examples 3, 4, 5 and 6, replace the term "Avail Mem Totals" 

contents with the following: 


Non Save 156,754,772 

Save 166,913,864 





o For examples 4, 5 and 6, replace the term "Spaces" with "Areas" 

in the heading as follows: 


"--- Total Words --" 

o Add CU AVAIL POOLS example 7 as follows: 

----------------------------- SYSTEM MEMORY USAGE - ... 

----- Memory Summary ---- --- ASD Information -- 

Available 440,930,713 Available 2,343,478 

Non save 47,204,160 In use 398,548 

Save 57,124,647 Maximum 408,283 

Total 545,259,520 Total 2,742,026 

Overlaid 0 In use 15% : Max 15% 

... ----------------------------- 


Non Save 421,388,917 

Save 317,350,749 




---------------------------- Memory Pools Summary ------- ... 

----- Memory Summary ---- ------------ Non Save Pools -- 

Available 520,720 Avail 1,270 211,632 

Non save 18,970,444 In use 224,594 18,970,444 

Save 4,565,468 Total 225,864 19,182,076 

Fragments 931,608 Fragments 3.25% 637,828 

268 6875 9497–003


Notlinked 451,560 Notlinked 1.86% 376,516 

Total 25,439,800 Areas 2,469 20,196,420 

Component: MESSAGES PRI-11459692 

Allow Message Suppression by Job Name 

... ----------------------- 

------- Save Pools ---- 

3,507 309,088 

65,290 4,565,468 

68,797 4,874,556 

6.05% 293,780 

1.43% 75,044 

641 5,462,116 

SYMPTOMS: 

Unable to suppress (or display) messages by job name. 


You can use the JOB keyword in an MSC command to identify a 

job name for which you want to suppress or display messages. 

Update the Menu-Assisted Resource Control (MARC) Ops Guide (form 

# 8600 0403) as follows: 

To the railroad diagram add: 

----- JOB ----- ---------------- 

Add the following entry to the MSC Command Message Type 

Specifications table: 

Type Messages Referenced 

JOB All messages from programs where the parent job 

has the designated job name 

Add the following entry to the Message ID FROM Qualifier Values 

table: 

Value Characteristic Common to Selected Messages 

JOB Specified job name 

The same changes apply to the description of the MSC (Message 

Control) system command in the System Commands Reference Manual 

(form # 8600 0395). 

6875 9497–003 269



Improve MCP MLS Messages 


Improve various MCP messages. 


Improve MLS Messages 


Make changes to the "System Messages Support Reference Manual" 

as follows. 

For the text of message MSRDPC208, replace "BASE UNIT" with 

"BASE PACK". 

For the text of message MSRDPC236, replace both instances of the 

word "UNIT" with "PACK". 

Put in the following new messages and explanations: 

PK IS NOT THE CORRECT BASE PACK FOR THE 

CONTINUATION VOLUME TO BE RESTORED.(DPC112) 

Cause 

An 'LB PK XM' system command failed because 

the base pack for the family does not match (the base pack may 

have been reconfigured with an RC system command). 

You will not be able to restore the continuation pack to the 

family with an LB system command. 

UNABLE TO OBTAIN UNIT STATUS(DPC95) 

Cause 

The system was trying to ready or test the unit, but the 

system was unable to determine the physical status of the 

unit. The system will mark the unit as UNLABELLED. 

Response 

Check for previous I/O error messages for the same unit. 

PK MIRRORED PACK BEING CREATED, APPLYING AUDIT, 

OR SET BROKEN BY LOADER.(DPC225) 

270 6875 9497–003


Cause 

During a mergeover, started by a SETSTATUS Type 5 (Unit Call) 

Subtype 38 (Mergeover) call, the system found a mirrored disk with 

a status that mergeover cannot handle. The indicated disk will 

not be merged-over. 

Response 

Note the error. 

Component: NETWORKING PRI-11552871 


interface 










Component: NETWORKING PRI-11554008 


interface 










6875 9497–003 271


Component: PHYSICALIO-DISK PRI-11487769 

Update Critical Unit Definition 

SYMPTOMS: 

Critical unit documentation is incomplete. 


MCP Implementation Guide 

6871 4260-002 

Replace the first paragraph in the "Mirroring System-Critical Disk 

Units" of section 4 with the following. 

If your system must maintain the highest reliability and 

availability, Unisys recommends that you mirror all system-critical 

disk units, with each mirror served by multiple online paths through 

at least two IOP cards on separate PCI buses. 

Add the follow new subsection prior to the "Mirroring System-Critical 

Disk Units" subsection. 

System-Critical Disk Units 

System-critical disk units are all disk units making up the Halt/load 

disk family, Overlay families (DL OVERLAY), Sumlog family (DL LOG), 

JOBS family (DL JOBS), CATALOG family (DL CATALOG), and STANDBY 

Halt/load unit families (CM + STANDBY). The use of RAID technology 

in the disk subsystem provides for continued availability of a disk 

unit in the event of a failure of a disk drive in the subsystem. 

Configuring multiple, independent paths to the disk subsystem 

provides continued availability of a disk unit if paths become 

unavailable as a result of maintenance actions or failure. 

Glossary for ClearPath MCP 

8807 6245-009 

Replace the definition of "critical unit" with the following. 

Critical disk units are all disk units making up the Halt/load disk 

family, Overlay families (DL OVERLAY), Sumlog family (DL LOG), JOBS 

family (DL JOBS), CATALOG family (DL CATALOG), and STANDBY Halt/load 

unit families (CM + STANDBY). 

272 6875 9497–003

Component: PORTS PRI-11493912 

ACTUALMYNAME File Attribute 


SYMPTOMS: 

The port number assigned by TCPIP to a port file cannot be 

determined. 


ACTUALMYNAME is a new readonly subport File Attribute. If the 

MYNAME port File Attribute is a null string and the service is 


returned. In all other cases the vale of the MYNAME attribute is 

returned. 

Add this description of the attribute to the File Attributes manual 

(86000064-511) : 

ACTUALMYNAME 

Kinds Port 


Modify Never 


Range Not applicable 


Abstract Value Not applicable 

Stored permanently No 

Parameters 1 

Heritage Host Services Logical I/O Not supported 

Port Services All 

If the MYNAME port File Attribute is a null string and the service is 


returned. In all other cases the value of the MYNAME File Attribute 

is returned. 

This attribute requires a subfile index as a parameter. 

Component: PROC-METERING PRI-11473865 

Allow Multiple E-OPTIONS Records In 

*METER/EMAIL/DESTINATIONS 


It is now possible to include multiple E-OPTIONS records in the 

*METER/EMAIL/DESTINATIONS file. This change requires the following 

update to section 7, Setting Up the MCP Partition, in the ClearPath 

6875 9497–003 273


Enterprise Servers MCP Resource Licensing Guide (68713130-002). 

Item 3 of the Installing Processing Power Metering subsection should 

be replaced with the following text. (NOTE: All single lines 

starting with 'E-OPTIONS', 'E-TASKFILE', 'E-FILE', or 'E-MAIL' must 

appear on a single line in the manual. For that reason, one of the 

E-OPTIONS lines is misaligned in the following text. This is done 

to show that line's contents as they should appear in the manual.) 

3. Create a *METER/EMAIL/DESTINATIONS file on the halt/load family. 

a. EMAIL normally runs with a usercode associated with it. 

However, when the system uses EMAIL to send a metering report, 

there is no usercode associated with it. To specify the email 

FROM address and, if needed, a LOGIN usercode and password (the 

information that would normally be in the user's USERDATA 

record or CANDE/MYOPTIONS file), the *METER/EMAIL/DESTINATIONS 

file should contain the following record: 

E-OPTIONS: FROM , LOGIN ""/"" 

If there are any problems sending the metering report, EMAIL 

will detect the error and create a printer backup TASKFILE of 

trace information. An E-TASKFILE record similar to the 

following should be added to the *METER/EMAIL/DESTINATIONS file 

to specify the directory for that TASKFILE: 

E-TASKFILE: (MY)METER/BD ON MYPACK 

In the rare case when EMAIL does not detect an error but there 

are still problems sending the report, temporarily add the 

TRACE option to the E-OPTIONS record to force EMAIL to create 

the TASKFILE. The TRACE option can be placed anywhere in the 

comma separated option list. For example: 

E-OPTIONS: FROM , TRACE, LOGIN ""/"" 

Refer to the definition of in the EMAIL Utility 

section of the System Software Utilities Operations Reference 

Manual for a full description of the list of options that could 

appear on an E-OPTIONS record. 

The *METER/EMAIL/DESTINATIONS file can contain multiple E-OPTIONS 

records if the does not fit on a single record. 

The following restrictions apply: 

- Each E-OPTIONS record must begin with a valid option 

- All options on a single E-OPTIONS record must be separated by 

a comma 

E-FILE records can be used to specify optional EMAIL files as 

well as modifying attributes of the SMTP server file. For 

example: 

274 6875 9497–003

E-FILE: SIGNATURE=(MY)FORMAL/SIGNATURE ON MYPACK 

E-FILE: SMTP(MYIPADDRESS = "172.20.71.149") 


Refer to the EMAIL Utility section of the System Software 

Utilities Reference Manual for applicable files. 

b. Optionally configure metering report destinations to have 

copies of the metering reports sent to alternate destinations. 

The file might contain the following record if the metering 

contract calls for metering reports to be sent to Unisys: 

E-MAIL: UNISYS 

The file may also contain the following E-MAIL records to 

send reports to single or multiple e-mail addresses. Each E-MAIL 

record should only contain one e-mail address. If the report 

needs to be sent to multiple addresses, the file should contain 

multiple E-MAIL records similar to the following: 

E-MAIL: 

E-MAIL: 

c. Optionally specify the metering report sending priority. The 

priority level ranges from 0 to 99, where priority level 0 

indicates that this partition will not send a report, priority 

level 1 is the lowest priority, and priority level 99 is the 

highest sending priority. If a priority level is not specified 

for a particular partition, the priority level is 99. Make sure 

that all partitions are not set to priority level 0 without prior 

agreement from Unisys marketing. If all partitions are set to 

priority 0, then alternate arrangements are required to ensure 

that the metering report is appropriately transferred to Unisys. 

Modify the *METER/EMAIL/DESTINATIONS file on the halt/load family 

and add a PRIORITY: record. 

The following shows an example of a *METER/EMAIL/DESTINATIONS file: 

E-MAIL: UNISYS 

E-MAIL: LocalGuy@ourcompany.com 

E-MAIL: AnotherGuy@ourcompnay.com 

E-OPTIONS: FROM LocalGuy@ourcompany.com 

E-OPTIONS: LOGIN ""/"" 

E-TASKFILE: METER/BD ON MYPACK 

E-FILE: SIGNATURE=(MY)FORMAL/SIGNATURE ON MYPACK 

E-FILE: SMTP(MYIPADDRESS = "172.20.71.149") 

PRIORITY: 85 

Any changes to the *METER/EMAIL/DESTINATIONS file become effective 

upon saving the file. 

6875 9497–003 275


Component: SCTABLEGEN PRI-11437869 








SYMPTOMS: 



















SYMPTOMS: 




276 6875 9497–003




keys that are due to expire in the near future. The warning message 

is: 









specified: 


+---- - -----+ 



is a number between 0 and 127. Setting WARNFACTOR to 0 disables 

the generation of warnings. 








Input 



TYPE 2 

SUBTYPE 111 



A [1] = 0 & 1 [38:06] 



to 30 days 

6875 9497–003 277


Call 


Results 


Example 


input: 

A [0] := 3; 

A [1] := 0 & 1 [38:06]; 

A [2] := 90; % Days 





includes: 




option 

0 = DONTCARE 

1 = NEVER 

2 = YES 





Operating System Information section of the Software Configuration 

(Type 17) call. 








and 

278 6875 9497–003







Cause 



Response 


















or REQUIRED: 


Telnet only offers connections over the non-secure port (default 








6875 9497–003 279


23) 




0 = Allowed 

1 = Disabled 

3 = Required 








or REQUIRED: 










23) 




0 = Allowed 

1 = Disabled 

3 = Required 

280 6875 9497–003

Component: SECURITY PRI-11476228 



SYMPTOMS: 













================ 




For example, 














================ 





6875 9497–003 281






















Node Item 

1 Local alias 








Privileged Processes Can Access Guarded Files 

SYMPTOMS: 

The Security Operations Guide (form # 8600 0528) contains a caution 

that is open to misinterpretation. 


Change the caution in the Understanding How a Guard File Works topic 

of the Operational Information for Guardfile topic of the Using 

Guard Files section in the Security Operations Guide (form # 8600 

0528) to: 

282 6875 9497–003


A privileged user or process bypasses the guard file for a 

GUARDED or CONTROLLED file. The file owner bypasses the 

guard file for a GUARDED file. All further discussion assumes 

that you are aware of these exceptions. 



SYMPTOMS: 












migration. 







The following explanation will be added to the System Log Programming 

Reference Manual (form # 8600 1807). 


Attribute) 






entry. 



words 

6875 9497–003 283






















or REQUIRED: 










23) 



284 6875 9497–003


0 = Allowed 

1 = Disabled 

3 = Required 









or REQUIRED: 










23) 




0 = Allowed 

1 = Disabled 

3 = Required 

Component: SYSTEMSTATUS PRI-11532373 

Remove Fine Priority From SYSTEMSTATUS Mix Requests 

SYMPTOMS: 

For a SYSTEMSTATUS type 27 (Mix Information) request, word 7 

of the General Mix Information incorrectly indicates the field 

6875 9497–003 285


[33:06] represents a task's Fine Priority. For type 27 

requests, the value returned in the Fine Priority field will 

always be zero. 

The outdated SYSTEMSTATUS type 3 (Mix Information) request 

available in SSR 52.1 and earlier releases also incorrectly 

indicates [33:06] of the STACKSTATUS word represent's the 

tasks Fine Priority. For type 3 requests, the value returned 

in the Fine Priority field may be non-zero. 


In the SYSTEMSTATUS Programming Reference Manual (8600 

0452-312): 

Section 18. Mix Information (Type 27) 

General Mix Information 

Please remove the following from the description of the fields 

in word 7 (STACKSTATUS): 

33:06 I Fine priority 

In the SSR 52.1 release, the SYSTEMSTATUS type 3 request is 

updated to no longer return information in the fine priority 

field. 

The SYSTEMSTATUS type 3 request does not require documentation 

updates to remove the fine priority field, since the type 3 

request is unavailable in SSR 53.1 and later releases. 












descriptions. 

286 6875 9497–003



descriptions. 














----------- 

| GS Word | 

----------- 

----------- 

| GS Word | 

----------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- 

| GS Word | 

----------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- ---------------------------- 


----------- ---------------------------- 




6875 9497–003 287









included. 


























288 6875 9497–003













descriptions. 


descriptions. 














----------- 

| GS Word | 

----------- 

----------- 

| GS Word | 

----------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- ---------------------------- 


----------- ---------------------------- 

6875 9497–003 289


----------- ---------------------------- 


----------- ---------------------------- 

----------- 

| GS Word | 

----------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- ---------------------------- 


----------- ---------------------------- 

----------- ---------------------------- 


----------- ---------------------------- 











included. 
















290 6875 9497–003













Memory Pools D-Note For SYSTEMSTATUS Manual 



0452-312), please add the following descriptions to: 

Section 3. Operational Group (Type 2) 


26 I POOLOLAYAVAIL 

27 I POOLSAVEAVAIL 

The number of words of available 

memory that are located in 

overlayable memory pools. This 

value represents a portion of the 

total available memory on the 

system. 

28 I POOLOLAYFRAGMENTED 


memory that are located in save 

memory pools. This value represents 

a portion of the total available 

memory on the system. 

The number of words of fragmented 

6875 9497–003 291


available memory in overlayable 

memory pools. 

29 I POOLSAVEFRAGMENTED 


available memory in save memory 

pools. 

39 I POOLSAVENOTLINKEDCORE 


memory in save memory pools that are 

not available for allocation. 

42 I POOLOLAYNOTLINKEDCORE 

43 I POOLAVAILCORE 

44 I POOLOLAYCORE 

45 I POOLSAVECORE 

74 I OLAYAREAS 

75 I SAVEAREAS 

76 I AVAILAREAS 


memory in overlayable memory pools 

that are not available for 

allocation. 

The sum of all available memory in 




The sum of all overlayable memory in 


a portion of the total overlayable 


The sum of all non-overlayable 

memory in memory pools. This value 

represents a portion of the total 

non-overlayable memory on the 

system. 

The number of non-save areas present in 

memory. 

The number of save areas present in 

memory. 

292 6875 9497–003

77 I OLAYAVAILAREAS 

78 I SAVEAVAILAREAS 

79 I NOTLINKEDAREAS 


The number of individual available areas 

in memory. 


in memory that are linked in the OLAY avail 

lists. 


in memory that are linked in the SAVE avail 

lists. 

The number of individual areas in memory 

that are available but too small to be 

allocated. 


Memory Pools D-Note For SYSTEMSTATUS Manual 



0452-312), please add the following descriptions to: 

Section 3. Operational Group (Type 2) 


26 I POOLOLAYAVAIL 

27 I POOLSAVEAVAIL 


memory that are located in 

overlayable memory pools. This 

value represents a portion of the 

total available memory on the 

system. 


memory that are located in save 




6875 9497–003 293


28 I POOLOLAYFRAGMENTED 


available memory in overlayable 

memory pools. 

29 I POOLSAVEFRAGMENTED 


available memory in save memory 

pools. 

39 I POOLSAVENOTLINKEDCORE 


memory in save memory pools that are 

not available for allocation. 

42 I POOLOLAYNOTLINKEDCORE 

43 I POOLAVAILCORE 

44 I POOLOLAYCORE 

45 I POOLSAVECORE 

74 I OLAYAREAS 

75 I SAVEAREAS 


memory in overlayable memory pools 

that are not available for 

allocation. 

The sum of all available memory in 




The sum of all overlayable memory in 


a portion of the total overlayable 


The sum of all non-overlayable 

memory in memory pools. This value 

represents a portion of the total 

non-overlayable memory on the 

system. 

The number of non-save areas present in 

memory. 

294 6875 9497–003

76 I AVAILAREAS 

77 I OLAYAVAILAREAS 

78 I SAVEAVAILAREAS 

79 I NOTLINKEDAREAS 

Component: TASKING PRI-11430562 

Remove IO Interrupt Strategy Value 


The number of save areas present in 

memory. 


in memory. 


in memory that are linked in the OLAY avail 

lists. 


in memory that are linked in the SAVE avail 

lists. 

The number of individual areas in memory 

that are available but too small to be 

allocated. 

SYMPTOMS: 

IOINTERRUPT is a long obsolete option to the SBP (System 

Balancing Parameters) command. 


In the GETSTATUS/SETSTATUS Programming Reference Manual 

(8600 0346-411) 

Section 3. GETSTATUS Request Type 2 (Miscellaneous Calls) 

Request Type 2 Calls By SUBTYPE 

SUBTYPE 4 Calls (System Balancing Parameters) 

Under the Results Returned heading, please remove the following 

entry: 

2 The IO Interrupt Strategy 

6875 9497–003 295



PROCESSINFO Task Attribute 

SYMPTOMS: 

It is not possible to determine whether a task has been initiated 

through PRIMITIVE RUN or AI (Automatic Initiation). 


The PROCESSINFO task attribute returns information about how a task 

was initiated. 

The following explanation will be added to the Task Attributes 


PROCESSINFO 

Type Real 

Units Not applicable 

Range See "Explanation" below 


Read Time Anytime 

Write Time Never 

Inheritance None 

Fork() Inheritance None 

Overwrite Rules None (read-only) 

Host Services Not supported 

Attribute Number 176 

Synonym None 

Restrictions Not available in WFL 

Explanation 

Example 

The PROCESSINFO task attribute records information about the 

process. The PROCESSINFO value is divided into the following 

fields: 

Field Name Meaning 

[00:01] AICALLF 1 if process was initiated as a result 

of an AI (Automatic Initiation) system 

command 

[01:01] PRIMCALLF 1 if process was initiated as a result 

of a PRIMITIVE RUN or ??RUN system 

command 

An ALGOL program can use a statement such as the following to 

determine it it was initiated as a result of an AI system 

command: 

296 6875 9497–003

IF BOOLEAN (MYSELF.PROCESSINFO) THEN ... 


The following explanation will be added to the SYSTEMSTATUS 


Mix Information (Type 27) 

Specific Mix Information 

Word Field Type Name and Meanding 

36 01:01 B TRUE if process was initiated as a 

result of PRIMITIVE RUN or ??RUN 

system command 

00:01 B TRUE if process was initiated as a 

result of an AI system command 


HISTORY_TEXT Interface in MCPSUPPORT Library 

SYMPTOMS: 

Some HISTORYREASON mnemonics, as documented in the Task Attributes 

Programming Reference Manual, are not easily understandable. 


The HISTORY_TEXT interface in the MCPSUPPORT library can be used to 

turn a history type, cause and reason into an English description 

(which is generally more understandable than the corresponding 

HISTORYREASON mnemonics). 

HISTORY_TEXT Procedure 

The HISTORY_TEXT procedure enables you to convert a history 

type, cause and reason into an English description. This 

description is the same as that shown by JOBFORMATTER, CANDE, 

and MARC for abnormal task terminations. 

Note: not all possible types, causes, and reasons are handled; 

the majority of common values are. 

Declaring the HISTORY_TEXT Procedure 

Declare the procedure in an ALGOL program as follows: 

LIBRARY MCPSUPPORT (LIBACCESS = BYFUNCTION); 

REAL PROCEDURE HISTORY_TEXT 

(TY, CZ, RSN, PLANG, LLANG, POUT, LOUT, OPTS, A); 

VALUE TY, CZ, RSN, PLANG, LLANG, POUT, OPTS; 

6875 9497–003 297


INTEGER TY, CZ, RSN, LLANG, LOUT; 

REAL OPTS; 

POINTER PLANG, POUT; 

ARRAY A [0]; 

LIBRARY MCPSUPPORT; 

HISTORY_TEXT Parameters 

The HISTORY_TEXT procedure includes the following parameters: 

Parameter Description 

TY HISTORYTYPE value 

CZ HISTORYCAUSE value 

RSN HISTORYREASON value 

PLANG Pointer to the language into which the 

history value is to be translated 

LLANG Length of the language string pointed to 

by the PLANG parameter 

POUT Pointer to where the description is to be 

placed 

LOUT An output parameter which is updated to the 

length of the description string 

OPTS Reserved 

A Reserved 

HISTORY_TEXT Procedure Result 

HISTORY_TEXT always returns 0. 

HISTORY_TEXT Procedure Example 

The following example shows code that uses the HISTORY_TEXT 

procedure to convert task history words into their expanded 

descriptions. 

BEGIN 

LIBRARY MCPSUPPORT (LIBACCESS = BYFUNCTION); 

REAL PROCEDURE HISTORY_TEXT 

(TY, CZ, RSN, PLANG, LLANG, POUT, LOUT, OPTS, A); 

VALUE TY, CZ, RSN, PLANG, LLANG, POUT, OPTS; 

INTEGER TY, CZ, RSN, LLANG, LOUT; 

REAL OPTS; 

POINTER PLANG, POUT; 

ARRAY A [0]; 

LIBRARY MCPSUPPORT; 

INTEGER LOUT; 

ARRAY A [0:0]; 

EBCDIC ARRAY HISTORYTEXT [0:99]; 

TASK T; 

PROCEDURE FAULT1; 

BEGIN 

298 6875 9497–003

ARRAY A [0:9]; 

A [10] := A[9]; % Invalid index 

END; 


PROCEDURE FAULT2; 

BEGIN 

FILE F (KIND = DISK, DEPENDENTSPECS, 

TITLE = "SYMBOL/HISTORY_TEXT."); 

OPEN (F); 

READ (F [F.LASTRECORD + 100]); % I/O err, end of file 

END; 

CALL FAULT1 [T]; 

HISTORY_TEXT (T.HISTORYTYPE, T.HISTORYCAUSE, 

T.HISTORYREASON, 

POINTER ("ENGLISH"), LENGTH ("ENGLISH"), 

HISTORYTEXT [0], LOUT, 0, A); 

DISPLAY (HISTORYTEXT [0]); 

CALL FAULT2 [T]; 

HISTORY_TEXT (T.HISTORYTYPE, T.HISTORYCAUSE, 

T.HISTORYREASON, 

POINTER (A), 0, 

HISTORYTEXT [0], LOUT, 0, A); 

% LLANG = 0 uses caller's language 

DISPLAY (HISTORYTEXT [0]); 

END. 

This program produces the following display: 

DISPLAY:F-DSED:Invalid Index. 

DISPLAY:I-DSED: Cause = 8 Reason = 88. 

Component: UNASSIGNED PRI-11449034 

Remove Code Segment Halt Feature 


The debugging commands ??HALT AT and ??HALT IN 

are no longer supported. 

6875 9497–003 299



Libra 780/790 Documentation 

SYMPTOMS: 

CS780/790 missing from numerous documents. 


This note describes the documentation changes for adding 

Libra 780 and Libra 790 machine names. 


Libra 780/790 Documentation 

SYMPTOMS: 

CS780/790 missing from numerous documents. 


This note describes the documentation changes for adding 

Libra 780 and Libra 790 machine names. 

Component: UTILITIES PRI-11472672 

Export Procedure GETMYCODEFILEHEADER 

SYMPTOMS: 

It is difficult for running code to determine attributes 

of the code file from which it is executing. 


A new procedure, GETMYCODEFILEHEADER, is exported from the 

MCPSUPPORT library. You can use it to obtain a copy of the 

disk file header of the code file from which the code 

calling GETMYCODEFILEHEADER is executing. 

(Note that the code file for a library procedure is the 

code file of the library, not the code file of the 

client process.) 

It can be declared as follows: 

300 6875 9497–003


LIBRARY MCP (LIBACCESS=BYFUNCTION,FUNCTIONNAME="MCPSUPPORT."); 

REAL PROCEDURE GETMYCODEFILEHEADER(A); 

ARRAY A[0]; 

LIBRARY MCP; 

It places a copy of the header into the array A. Attributes of 

the header can then be determined using the GETHEADERATTRIBUTE 

procedure also exported from the MCP. 

The value returned by the procedure consists of two fields: 

Field Contents 

[23:16] If the field [7:8] contains the value 0, 

the size in words of the header returned. 

If the field [7:8] contains the value 2, 

the required size in words of the array to be passed. 

Otherwise undefined and should not be used. 

[ 7: 8] 0 if the header was returned. 

The size of the header in words is in field [23:16]. 

1 if an internal error prevented the header from 

being obtained in the proper format. 

2 if the size of the array was insufficient 

to return the header. 

The necessary size in words is in field [23:16]. 

3 if an internal fault occurred. 


Export Procedure GETMYCODEFILEHEADER_STAR 

SYMPTOMS: 

A Pascal program cannot call the MCP procedure GETMYCODEFILEHEADER. 


A new procedure, GETMYCODEFILEHEADER_STAR, is exported from the 

MCPSUPPORT library. You can use it to obtain a copy of the 

disk file header of the code file from which the code 

calling GETMYCODEFILEHEADER is executing. 

(Note that the code file for a library procedure is the 

6875 9497–003 301


code file of the library, not the code file of the 

client process.) 

It can be declared as follows: 

LIBRARY MCP (LIBACCESS=BYFUNCTION,FUNCTIONNAME="MCPSUPPORT."); 

REAL PROCEDURE GETMYCODEFILEHEADER_STAR(A,A_SIZE); 

VALUE A_SIZE; 

ARRAY A[*]; 

INTEGER A_SIZE; 

LIBRARY MCP; 

It places a copy of the header into the array A. Attributes of 

the header can then be determined using the GETHEADERATTRIBUTE 

procedure also exported from the MCP. 

The caller must pass the size of the array as A_SIZE. 

The value returned by the procedure consists of two fields: 

Field Contents 

[23:16] If the field [7:8] contains the value 0, 

the size in words of the header returned. 

If the field [7:8] contains the value 2, 

the required size in words of the array to be passed. 

Otherwise undefined and should not be used. 

[ 7: 8] 0 if the header was returned. 

The size of the header in words is in field [23:16]. 

1 if an internal error prevented the header from 

being obtained in the proper format. 

2 if the size of the array was insufficient 

to return the header. 

The necessary size in words is in field [23:16]. 

3 if an internal fault occurred. 

302 6875 9497–003



ASERIES_INFO Reports PROTECTION, PROTECTIONVALUE 


Two new attributes have been added to the Disk scope 

of ASERIES_INFO, as follows: 

Information 

Name Type Number Returned 

PROTECTION String 190 The mnemonic value of the 

------- PROTECTION file attribute 

of the file. 

(Since ASERIES_INFO reports on 

permanent files in the disk 

directory, a value of 

TEMPORARY will not be seen.) 

PROTECTIONVALUE Integer 191 The integer value of the 

----------- PROTECTION file attribute 

of the file. 

MCPJAVA 

Component: INFRASTRUCTURE PRI-11465692 

Add support for control key-ins 

(Since ASERIES_INFO reports on 

permanent files in the disk 

directory, a value of 0 

(TEMPORARY) will not be seen.) 

SYMPTOMS: 

On Unix and Windows platforms Sun JVMs support unsolicited key-ins 

to display status of threads and memory or to gracefully shutdown 

the JVM. These commands were not implemented for MCP Java. 


This patch adds several new options to the existing NA JAVA and AX 

commands. 

JAVA KILL COMMAND 

This command terminates a Java program immediately, by stopping the 

Java proxy running on MCP. 

6875 9497–003 303


--- NA JAVA ----- KILL -- ---| 

JAVA CANCEL COMMAND 

This command terminates a Java program gracefully. The program is 

signalled to initiate a shutdown and any registered shutdown hooks 

are called. This is equivalent to the Ctrl-C option with a 

Windows JVM. 

--- NA JAVA ----- CANCEL -- ---| 

AX QUIT COMMAND 

The QUIT command command terminates a Java program gracefully. 

The program is signalled to initiate a shutdown and any registered 

shutdown hooks are called. This is equivalent to the Ctrl-C option 

with a Windows JVM. 

The QUIT NOW command immediately terminates the Java application 

currently running on the JVM. 

--- AX --- QUIT -----------------------| 

|-- NOW --| 

AX CANCEL COMMAND 

The CANCEL command is a synonym for the QUIT command. 

--- AX --- CANCEL -----------------------| 

AX KILL COMMAND 

The KILL command is a synonym for the QUIT NOW command. 

--- AX --- KILL -----------------------| 

AX STATUS COMMAND 

The STATUS command displays the current execution stack and other 

information about each of the Java threads in the program. With 

some versions of Java, it will also display information about locks 

and memory usage. 

This option may not be available with all versions of the JVM. 

--- AX --- STATUS -----------------------| 


Disable editing the device number value in JavaConfig 

SYMPTOMS: 

Setting the device number in the Java Config utility could lead to 

inconsistent IP addresses being used with multiple JProcessors. 

304 6875 9497–003



The Device Number field in the Java Configuration tool dialog box 

is now a display-only field. The device number may be set using 

the Appliance Configuration tool, as described in the 

"Configuring the Device" section of the ClearPath Common Appliance 

Configuration Guide (8212 4678). 


Add Pseudo DNS names for EVLAN endpoints. 

SYMPTOMS: 

Currently the way to use socket optimization is by specifying the 

explicit EVLAN addresses for the JDP. These addresses are different 

for each JDP, so if you run your application in a pool of JDPs, you 

can't know in advance which EVLAN address will be correct. 


Two built-in DNS names may be used to specify the endpoints of 

the EVLAN connection between the Java Server and the MCP host. 

These names may be used with socket optimization to specify the 

optimized network path without needing to know the actual IP 

address of the Java Server. 

EVLANMCP names the MCP host connection to the EVLAN. Use this 

name when connecting to a database or other application running 

on the host. 

EVLANJDP names the Java Server endpoint of the EVLAN. Use this 

name if the Java program will be listening for connections from 

other applications running on the MCP host. 

(The names are not case-sensitive.) 


Set Windows recovery options for the Java Monitor service. 

SYMPTOMS: 

If the Java Monitor service stopped unexpectedly, it would not 

restart unless someone manually restarted it using Remote Desktop 

to the Java Processor. 


When the Unisys MCP Java Configuration Utility is run, it will 

check the service recovery settings for the Java Monitor. If they 

are not set, it will set them to following three values: 

1. Restart the service. 


3. Restart the computer (unless VM system). 

When MCP Java is running on a VM system (Libra 400/450 or LX) the 

6875 9497–003 305


third option will be "Take No Action". 

If the recovery options have been set previously, to any values other 

than "Take No Action", the Java Configuration Utility will not 

modify the values. 

You must be an administrator to run the Java Configuration Utility. 


Set Windows recovery options for the Java Monitor service. 

SYMPTOMS: 

If the Java Monitor service stopped unexpectedly, it would not 

restart unless someone manually restarted it using Remote Desktop 

to the Java Processor. 


When the Unisys MCP Java Configuration Utility is run, it will 

check the service recovery settings for the Java Monitor. If they 

are not set, it will set them to following three values: 



3. Restart the computer (unless VM system). 

When MCP Java is running on a VM system (Libra 400/450 or LX) the 

third option will be "Take No Action". 

If the recovery options have been set previously, to any values other 

than "Take No Action", the Java Configuration Utility will not 

modify the values. 

You must be an administrator to run the Java Configuration Utility. 

Component: JAVAIO PRI-11594476 

Allow FILEEQUATE on new JAVA files to expand their size 

SYMPTOMS: 

By default, files created by a Java application have an AREASIZE 

of 1024 sectors. This limits the size of files, particularly 

JAR files. 


The JAVAIO library will now extract the last node name of files 

being opened as new files and use that name as an INTNAME to 

check to see if any of the following file attributes have been 

equated and assign those values to the new file. While many 

306 6875 9497–003


other attributes exist, because JAVA files are stream files, many 

attribute values are effectively predefined. 

AREALENGTH 

AREAS 

BUFFERS 

BUFFERSIZE 

CLEARAREAS 

FAMILYINDEX 

NOTE 

For example, in WFL: 

RUN *DIR/JRE6/BIN/JAR ("-cvf myfiles.jar /-/JAVA/DIR/USER/ ."); 

FILE #"MYFILES.JAR" 

(AREALENGTH=737280, NOTE="INTNAME EQUATED TO MYFILES.JAR"); 

The last node of the filename will be truncated to 17 characters. 

Only characters allowed in an INTNAME can be used. A recommendation 

is to use the characters A-Z, numbers 0-9, the period, hyphen 

and underscore. 


Allow FILEEQUATE on new JAVA files to expand their size 

SYMPTOMS: 

By default, files created by a Java application have an AREASIZE 

of 1024 sectors. This limits the size of files, particularly 

JAR files. 


The JAVAIO library will now extract the last node name of files 

being opened as new files and use that name as an INTNAME to 

check to see if any of the following file attributes have been 

equated and assign those values to the new file. While many 

other attributes exist, because JAVA files are stream files, many 

attribute values are effectively predefined. 

AREALENGTH 

AREAS 

BUFFERS 

BUFFERSIZE 

CLEARAREAS 

FAMILYINDEX 

NOTE 

For example, in WFL: 

RUN *DIR/JRE6/BIN/JAR ("-cvf myfiles.jar /-/JAVA/DIR/USER/ ."); 

FILE #"MYFILES.JAR" 

(AREALENGTH=737280, NOTE="INTNAME EQUATED TO MYFILES.JAR"); 

6875 9497–003 307


The last node of the filename will be truncated to 17 characters. 

Only characters allowed in an INTNAME can be used. A recommendation 

is to use the characters A-Z, numbers 0-9, the period, hyphen 

and underscore. 


INTNAME can only contain Characters, numbers, hypen, 

underscore 

SYMPTOMS: 

Setting INTNAME when running the JCK causes some INTNAME warnings. 


The 'expected' INTNAME is scanned for the allowable characters. 

Component: JAVAPROXY PRI-11543260 

Exitcodes 129-150 are usually valid values, not negative 

SYMPTOMS: 

When JAVA is interrupted, e.g., with an AX QUIT, the EXITCODE 

returned is the value of the signal + 128. 


The JBoss RUN WFL has been modified to test for EXITCODE values 

greater than 150 as 2's complement negative values. 

The Java Proxy has been modified to recognize the appropriate 

signal exits and terminate accordingly. 

The Virtual Machine for the Java 5.0 and 6.0 Platform on 

ClearPath MCP 12.1 Programming Guide will be updated to reflect 

this information in the section "Differences from Traditional MCP 

Applications" as follows: 

- Under Subheading 'Exit Codes' change the paragraph to read: 

When a Java application finishes, it can optionally return an 

exit code. The exit code is returned in bits [15:8] of the 

application's TASKVALUE. The exit code values range from -127 

to 127 with negative values being stored in two's complement 

format. 

When the JVM is terminated by a 'signal' prior to a 'normal' 

end-of-job, it will set the exit code to a value of 129-150 

308 6875 9497–003


inclusive. Because negative values are stored in two's 

complement format, these values cannot be distinguished from 

negative values, e.g., -126 and 130 are both represented in 8 

bits as 0x82. 

From this value, you can identify the signal that caused the 

termination. For example, when you enter AX QUIT, this 

causes the SIGINT signal to be raised and the JVM terminates 

with an exit code of 130. The following table identifies the 

signals and their corresponding exit code: 

Signal Exit Code Description 

--------- --------- ------------------------ 

SIGINT 130 Terminal interrupt 

SIGILL 132 Illegal instruction 

SIGFPE 136 Floating point exception 

SIGSEGV 139 Segment violation 

SIGTERM 143 Software termination 

SIGABRT 150 Abnormal termination 

Because of this, you should not set exit codes to the 

negative values from -106 to -127. 

The following WFL subroutine can be used to retrieve the exit 

code from the TASKVALUE of a Java application. 

- Change the example in this subsection to read: 

SUBROUTINE GETEXITCODE (TASK T, INTEGER EXITCODE); 

% GETEXITCODE accepts a TASK variable and extracts the Java 

% exitcode from the TASKVALUE. If the exitcode was negative, 

% the value is stored as an 8-bit two's complement value. 

% Exitcodes range from -127 to 127. The exitcode is found in 

% bits 15:8 of the TASKVALUE word. 

BEGIN 

EXITCODE := T(TASKVALUE) / 256; 

IF EXITCODE GTR 150 THEN 

% Errors caused by SIGNALS, e.g., SIGTERM, will be 

% result in exit codes 129-150. For example, 

% AX QUIT raises SIGINT and returns 130. 

EXITCODE := EXITCODE - 256; 

END GETEXITCODE; 

- Add the following entry to the table of exit codes: 

-93 The JAVASUPPORT library terminated while the JVM 

was executing. 


6875 9497–003 309


Exitcodes 129-150 are usually valid values, not negative 

SYMPTOMS: 

When JAVA is interrupted, e.g., with an AX QUIT, the EXITCODE 

returned is the value of the signal + 128. 


The JBoss RUN WFL has been modified to test for EXITCODE values 

greater than 150 as 2's complement negative values. 

The Java Proxy has been modified to recognize the appropriate 

signal exits and terminate accordingly. 

The Virtual Machine for the Java 5.0 and 6.0 Platform on 

ClearPath MCP 12.1 Programming Guide will be updated to reflect 

this information in the section "Differences from Traditional MCP 

Applications" as follows: 

- Under Subheading 'Exit Codes' change the paragraph to read: 

When a Java application finishes, it can optionally return an 

exit code. The exit code is returned in bits [15:8] of the 

application's TASKVALUE. The exit code values range from -127 

to 127 with negative values being stored in two's complement 

format. 

When the JVM is terminated by a 'signal' prior to a 'normal' 

end-of-job, it will set the exit code to a value of 129-150 

inclusive. Because negative values are stored in two's 

complement format, these values cannot be distinguished from 

negative values, e.g., -126 and 130 are both represented in 8 

bits as 0x82. 

From this value, you can identify the signal that caused the 

termination. For example, when you enter AX QUIT, this 

causes the SIGINT signal to be raised and the JVM terminates 

with an exit code of 130. The following table identifies the 

signals and their corresponding exit code: 

Signal Exit Code Description 

--------- --------- ------------------------ 

SIGINT 130 Terminal interrupt 

SIGILL 132 Illegal instruction 

SIGFPE 136 Floating point exception 

SIGSEGV 139 Segment violation 

SIGTERM 143 Software termination 

SIGABRT 150 Abnormal termination 

Because of this, you should not set exit codes to the 

negative values from -106 to -127. 

The following WFL subroutine can be used to retrieve the exit 

code from the TASKVALUE of a Java application. 

310 6875 9497–003

- Change the example in this subsection to read: 


SUBROUTINE GETEXITCODE (TASK T, INTEGER EXITCODE); 

% GETEXITCODE accepts a TASK variable and extracts the Java 

% exitcode from the TASKVALUE. If the exitcode was negative, 

% the value is stored as an 8-bit two's complement value. 

% Exitcodes range from -127 to 127. The exitcode is found in 

% bits 15:8 of the TASKVALUE word. 

BEGIN 

EXITCODE := T(TASKVALUE) / 256; 

IF EXITCODE GTR 150 THEN 

% Errors caused by SIGNALS, e.g., SIGTERM, will be 

% result in exit codes 129-150. For example, 

% AX QUIT raises SIGINT and returns 130. 

EXITCODE := EXITCODE - 256; 

END GETEXITCODE; 

- Add the following entry to the table of exit codes: 

-93 The JAVASUPPORT library terminated while the JVM 

was executing. 


Add ARGS file to proxy to allow for MANY Java parameters 

SYMPTOMS: 

WFL has a limit of 1024 bytes in a STRING. Attempting to run 

applications like GLASSFISH from a WFL cannot be done because 

there is no way to pass the long list of needed parameters, 

particularly the Environment Variables needed to run the application. 


A new file, ARGS, has been added to the Java proxy. When this 

file is equated, it will be opened and its contents PREPENDED 

to the Java runtime parameters. The file containing additional 

arguments can be any kind of 'symbol' record-oriented file, e.g., 

SEQDATA, a stream file, e.g., a file created on a disk share with 

Windows Notepad, a WFL 'data file', etc. Use of this file requires 

either the KIND or FILENAME (TITLE, LTITLE or PATHNAME) attributes 

to be equated. For example: 

RUN JAVA (""); FILE ARGS (READER); 

RUN JAVA (""); FILE ARGS (FILENAME=MYPARAMS); 

If the file is a record file, such as a SEQDATA file, a space is 

added between records. Long values can be continued across records 

by using the backslash to indicate 'continued on the next record. 

For example, given the following four records (where the first 

6875 9497–003 311


non-blank character is the first character of each record) 

-Djavatest.security.allowPropertiesAccess=true 

-Djava.rmi.activation.port=1270 

-Dunisys.mcp.io.correctFileSeparator\ 

=true 

would result in the following three parameters prepended to the 

Java parameter string. 



-Dunisys.mcp.io.correctFileSeparator=true 

When the argument file is a stream file, it is assumed that 

parameters are NOT split across 'records'. The line separators 

are simply translated into spaces. 

The following are examples of how to use the ARGS file: 

RUN *DIR/JRE6/BIN/JAVA ON JAVA6 ("MyClass"); 

FILE ARGS (TITLE=*DIR/JAVA/"ASENV.VARS" ON JAVA6); 

Or from a WFL job: 

RUN *DIR/JRE6/BIN/JAVA ("MyClass"); 

FILE ARGS (READER); 

DATA ARGS 




? 

By using the ARGS file to pass parameters to the JVM, the parameter 

string size limitation has been increased from 1024 bytes to 

32400 bytes. 


Add ARGS file to proxy to allow for MANY Java parameters 

SYMPTOMS: 

WFL has a limit of 1024 bytes in a STRING. Attempting to run 

applications like GLASSFISH from a WFL cannot be done because 

there is no way to pass the long list of needed parameters, 

particularly the Environment Variables needed to run the application. 


A new file, ARGS, has been added to the Java proxy. When this 

file is equated, it will be opened and its contents PREPENDED 

to the Java runtime parameters. The file containing additional 

312 6875 9497–003


arguments can be any kind of 'symbol' record-oriented file, e.g., 

SEQDATA, a stream file, e.g., a file created on a disk share with 

Windows Notepad, a WFL 'data file', etc. Use of this file requires 

either the KIND or FILENAME (TITLE, LTITLE or PATHNAME) attributes 

to be equated. For example: 

RUN JAVA (""); FILE ARGS (READER); 

RUN JAVA (""); FILE ARGS (FILENAME=MYPARAMS); 

If the file is a record file, such as a SEQDATA file, a space is 

added between records. Long values can be continued across records 

by using the backslash to indicate 'continued on the next record. 

For example, given the following four records (where the first 

non-blank character is the first character of each record) 



-Dunisys.mcp.io.correctFileSeparator\ 

=true 

would result in the following three parameters prepended to the 

Java parameter string. 




When the argument file is a stream file, it is assumed that 

parameters are NOT split across 'records'. The line separators 

are simply translated into spaces. 

The following are examples of how to use the ARGS file: 

RUN *DIR/JRE6/BIN/JAVA ON JAVA6 ("MyClass"); 

FILE ARGS (TITLE=*DIR/JAVA/"ASENV.VARS" ON JAVA6); 

Or from a WFL job: 

RUN *DIR/JRE6/BIN/JAVA ("MyClass"); 

FILE ARGS (READER); 

DATA ARGS 




? 

By using the ARGS file to pass parameters to the JVM, the parameter 

string size limitation has been increased from 1024 bytes to 

32400 bytes. 

Component: JNI PRI-11459331 

6875 9497–003 313


Enable JNI Support for user-written code. 

SYMPTOMS: 

JNI was not previously available. 


This is the initial release of JNI. See the online help for 

a detailed explanation. 

Component: JNI PRI-11459684 

Enable JNI Support for user-written code. 

SYMPTOMS: 

JNI was not previously available. 


This is the initial release of JNI. See the online help for 

a detailed explanation. 

Component: MCPJAVA PRI-11462006 

Mechanism to allow STDOUT/STDERR remote output to PAUSE 

SYMPTOMS: 

Often times the STDOUT/STDERR output to a CANDE station goes to 

fast or is too much to fit on one screen. There needs to be a 

mechanism, like the /P function in the Windows DIR command, that 

will allow you to stop the application and continue at 'your own 

pace'. 


MCPJAVA has been modified to allow a 'pause' parameter to be 

passed to the JAVA proxy via the task attribute TASKSTRING. E.g., 

RUN *DIR/JRE/BIN/JAVA (""); TASKSTRING="/pause"; 

The syntax for the 'pause' parameter requires a leading slash (/) 

or hyphen (-), followed by a P or the word PAUSE, in either upper 

or lower case. Additionally, the P or PAUSE can be followed by 

'=STDOUT' or '=STDERR' to indicate that only one of the output 

files is to be paused. If neither STDOUT or STDERR are specified, 

both are paused. 

--+-- / --+--+-- PAUSE --+--+-----------------| 

| | | | | | 

+-- - --+ +-- P ------+ +-- =STDOUT --+ 

314 6875 9497–003

| | 

+-- =STDERR --+ 


Note that there are no spaces between the parts of the 'pause' 

option. For example: 

/p 

-PAUSE 

-p=STDOUT 

/PAUSE=STDERR 

When the output pauses, the message 

" Transmit a space to continue, ?END to continue without pausing" 

is displayed on the screen. Transmitting a space will cause the 

application to continue. Transmitting a non-space will flush the 

remaining output buffer and the string "*BREAK*" will be displayed 

on the screen. When "?END" is transmitted, the pause function is 

turned off; the program will continue uninterrupted. 

MCP-WORKLOADMGR 

Component: WLMSUPPORT PRI-11551963 

Increase Allowed Statistics File Retention Period 

SYMPTOMS: 

The current limit for retention of statistics files is 366 days. 

We would like to allow a higher limit and furthermore allow for 

no limit, meaning infinite retention. 


The maximum retention period for statistics files has been 

increased from the current limit of 366 days to 999 days. A value 

of zero is now permitted; this will indicate that files are to be 

retained indefinitely. 

6875 9497–003 315


Component: WLMSUPPORT PRI-11551971 

Increase Allowed Statistics File Retention Period 

SYMPTOMS: 

The current limit for retention of statistics files is 366 days. 

We would like to allow a higher limit and furthermore allow for 

no limit, meaning infinite retention. 


The maximum retention period for statistics files has been 

increased from the current limit of 366 days to 999 days. A value 

of zero is now permitted; this will indicate that files are to be 

retained indefinitely. 

Component: WORKLOADCENTER PRI-11413196 

Implementation Of Process Monitor 

SYMPTOMS: 

The existing Workload Center does not have any feature to present 

real time information about processes associated with workload 

groups 

in a manner easily interpreted by system administrators. 


A third tree node named "Process Monitor" has been added as a sub 

node under the Performance Monitors node. 

On clicking on the Process Monitor node, a tabular view of the 

process statistics as well as a graphical view is being displayed 

in the result pane. A dropdown listing of all the available 

workload groups on the host is being displayed on the top status 

bar. The user can select any one workload group and view its 

statistics. 

The tabular view lists the processes belonging to the selected 

workload group and is being updated at every monitor update 

interval. The status bar at the bottom of the window displays the 

number of processes present in the listview. Each list entry in the 

view would present the following data: 

mix number, process name, I/O rate, CPU rate, and DMS rate. A user 

may sort the contents of the list by any of the data types. In case 

a process is added or removed from the workload group due to the 

modification in the related membership rule or due to the exit of 

the process, etc, the same is being reflected (as either visible or 

not visible) in the results pane of the process monitor, in the 

next polling interval. 

316 6875 9497–003


The tabular view also has a row at the end of the list of processes 

to display the totals of the CPU Rate, IO rate and DMS Rate 

consumed by the workload group. 


Clarify Privilege Requirements to Use Workload Center 

SYMPTOMS: 

The Workload Management for ClearPath MCP User's Guide, form 

#3850-8115, indicates that only system administrator usercodes 

(meaning usercodes with the SYSADMIN attribute) are able to run 

Workload Center. This is incorrect, as both privileged usercodes and 

system user usercodes are also able to run Workload Center. 


Three types of usercode are able to run Workload Center in MCP 

releases at and prior to MCP 12.0 (53.1). A privileged user, system 

user, or system administrator can all use Workload Center 

functionality. Note that this is subject to change. 

A privileged user is a usercode with the PU attribute, a system user 

is a usercode with the SYSTEMUSER attribute, and a system 

administrator is a usercode with the SYSADMIN attribute. 


Client Tracing Capabilities 

SYMPTOMS: 

Earlier Workload Center was not able to generate human readable text 

showing the code execution path either on-demand or when significant 

events occur. 

This is the enhancement to the Tracing Capabilities of the MCP 

Workload Center. 


Menu items "Trace To File", "Stop Tracing" and 

"Generate UCF Materials" have been added to the main menu 

Tools-->Debug. The menu item "Stop Tracing" will be disabled 

initially and will be enabled as soon as the tracing started and the 

menu item "Trace To File" will be disabled once tracing started and 

will be enabled once tracing is stopped. 

1. If Workload Center encounters a critical error or unhandled 

6875 9497–003 317


exception, a text file is created with a name generated from the date 

and time. The file contains the version information for WLMSUPPORT, 

Workload Center, and MCPInfo. The entire contents of the trace buffer 

are written to the file in chronological order. The file is located 

under "\Documents and Settings\\Local Settings\Application 

Data\Unisys Corporation\Workload Center". 

2. The menu item called "Generate UCF Materials" can be used to 

force the creation of the file described above. 

3. A menu item called "Trace to file" will be available. When 

activated, it queries the user for a file name. After a filename is 

specified, all Trace data is mirrored to the file for the entire 

Workload Center session. 


Support For Binary Statistics File Format 

SYMPTOMS: 

Support a new binary format for more efficient extraction and 

processing of Statistics Report data based on fixed-format data 

records. Also Workload Center should interoperate with old MCP hosts 

and MCPInfo dll not supporting binary statistics data. 


Now Workload Center supports extraction and processing of Statistics 

Report data in binary format. It will also interoperate with old MCP 

hosts and MCPInfo dll not supporting binary statistics data. 



SYMPTOMS: 






By default, the Workload Center installation installs a 32-bit 





318 6875 9497–003






32-bit applications (such as Workload Center) use the 32-bit version, 

and 64-bit applications (such as Windows Explorer) use the 64-bit 

version. 


Configuration Dialog For Client Tracing 

SYMPTOMS: 

There was no functionality available to configure the Client Tracing. 


A new dialog was created to configure the Trace Level and Trace with 

Time Stamp options for Client Tracing. 


LOAD/CONFIGURATION/PARAMETERS/RESULT 

SYMPTOMS: 

If the user attempts to load a configuration file that does not 

exist, the error dialog box displays a message that includes only 

part of the nonexistent path. 


Added internal logic to detect this situation and format the error 

message appropriately. 


Descriptive error messages for missing configuration parameters 

files. 

SYMPTOMS: 

If the user attempts to load a configuration parameters file that 

does not exist, the error dialog box message does not indicate that 

the parameters file specifically is missing. 

6875 9497–003 319



Added internal logic to detect this situation and format the error 

message appropriately. 

MESSAGESUPPORT 

Component: MESSAGESUPPORT PRI-11459706 

Allow Message Suppression by Job Name 

SYMPTOMS: 

Unable to suppress (or display) messages by job name. 


You can use the JOB keyword in an MSC command to identify a 

job name for which you want to suppress or display messages. 

Update the Menu-Assisted Resource Control (MARC) Ops Guide (form 

# 8600 0403) as follows: 

To the railroad diagram add: 

----- JOB ----- ---------------- 

Add the following entry to the MSC Command Message Type 

Specifications table: 

Type Messages Referenced 

JOB All messages from programs where the parent job 

has the designated job name 

Add the following entry to the Message ID FROM Qualifier Values 

table: 

Value Characteristic Common to Selected Messages 

JOB Specified job name 

The same changes apply to the description of the MSC (Message 

Control) system command in the System Commands Reference Manual 

(form # 8600 0395). 

320 6875 9497–003

MQMCP 

Component: API PRI-11431992 

Implement Use of the WinRPC Client Fast Interface 


SYMPTOMS: 

In previous releases, the WinRPC client fast interface is a keyed 

feature. This feature will be available without a key starting 

with release 54.1. There is a performance advantage to using the 

WinRPC client fast interface. 


Make the following change to the WebSphere MQ for ClearPath MCP 

User's Guide (8999 8983): 

NEWP 

Add the following to the table in Section 10. Troubleshooting/ 

Understanding Reason Codes/MQAPI Support Library Reason Codes: 

-5014 Indicates that the connection to WinRPC failed. 

Component: NEWP PRI-11426671 

Remove 2's Complement (INT32) Types 


Disregard D-NOTE PRI-11136681 INT32/INT64CONVERT/DNOTE [00NEWP]. 

Because of a change in direction, 32-bit and 64-bit 

2's complement operators are no longer available for E-mode level 

Zeta. 

The INT32 type and INT32 expressions are no longer available. 

Two's complement functions and intrinsics are no longer available. 


Documentation Unclear for Array Dimension Subtype Mismatch 

SYMPTOMS: 

The compiler does not generate diagnostics for array dimensions 

that are defined by a , but for which a type that is 

considered type compatible was used in the array reference. 

6875 9497–003 321



The documentation for Type Checking for Array subscripts indicates 

that only subscripts corresponding to an dimension 

must be of the same type as the dimension. A subscript that 

corresponds to a dimension must be type compatible with 

the dimension. Items are type compatible if they are descended 

from the same base type. Real and Integer base types are considered 

type compatible. 


GETINDEX and GETELEMENTSIZE Intrinsics 


In the NEWP Programming Reference Manual (8600 2003-404) Section 8 

UNSAFE Mode, Intrinsics (UNSAFE) add the following: 

GETELEMENTSIZE [MACHINEOPS] 

---- GETELEMENTSIZE ( ) -------------> 

GETELEMENTSIZE is an integer intrinsic that applies the GESZ 

operator to the parameter. It returns the element size of the 

descriptor. 

GETINDEX [MACHINEOPS] 

---- GETINDEX ( ) -------------------> 

GETINDEX is an integer intrinsic that applies the GINX operator 

to the parameter. It returns the virtual index of the descriptor. 


GETINDEX and GETELEMENTSIZE Intrinsics 


In the NEWP Programming Reference Manual (8600 2003-404) Section 8 

UNSAFE Mode, Intrinsics (UNSAFE) add the following: 

GETELEMENTSIZE [MACHINEOPS] 

---- GETELEMENTSIZE ( ) -------------> 

GETELEMENTSIZE is an integer intrinsic that applies the GESZ 

operator to the parameter. It returns the element size of the 

descriptor. 

322 6875 9497–003

GETINDEX [MACHINEOPS] 


---- GETINDEX ( ) -------------------> 

GETINDEX is an integer intrinsic that applies the GINX operator 

to the parameter. It returns the virtual index of the descriptor. 

NX/COMSCENTER 

Component: COMSCENTER PRI-11563031 

Implement the the COMS Update Command and Pass Command 

SYMPTOMS: 

The Update Command and Pass Command need to be added to the 

Operations Menu. 


The COMS Update command and program agent Pass command have been 

added to COMSCenter. 

The Update Command needs a help screen to document this command. 

Several field level (context-sensitive) help IDs are also required. 

The D-Note that implements this command in COMS is PRI-11490531. 

The program agent Pass Command needs a help screen to document 

this command. Several field level (context-sensitive) help IDs 

are also required. The D-Note that implements this command in 

COMS is PRI-11484026 and PLE 18688841. 

Component: COMSCENTER PRI-11563058 

Implement the the COMS Update Command and Pass Command 

SYMPTOMS: 

The Update Command and Pass Command need to be added to the 

Operations Menu. 


The COMS Update command and program agent Pass command have been 

added to COMSCenter. 

The Update Command needs a help screen to document this command. 

Several field level (context-sensitive) help IDs are also required. 

The D-Note that implements this command in COMS is PRI-11490531. 

6875 9497–003 323


The program agent Pass Command needs a help screen to document 

this command. Several field level (context-sensitive) help IDs 

are also required. The D-Note that implements this command in 

COMS is PRI-11484026 and PLE 18688841. 

Component: NX/COMSCENTER PRI-11554377 

Allow Selected Stations In Station Search Form To Be Copied 

SYMPTOMS: 

There is no way to copy all or part of the list of stations that 

are to be deleted in the Station Search form. 


When Options --> Station Search... is selected, the Search 

Stations form is presented. A new command button has been added 

to this form directly below the list of stations that are to 

be deleted. 

When clicked, any selected stations in the to-be-deleted list are 

copied to the clipboard. This information can then be pasted to a 

screen or to a file. 


Allow Selected Stations In Station Search Form To Be Copied 

SYMPTOMS: 

There is no way to copy all or part of the list of stations that 

are to be deleted in the Station Search form. 


When Options --> Station Search... is selected, the Search 

Stations form is presented. A new command button has been added 

to this form directly below the list of stations that are to 

be deleted. 

When clicked, any selected stations in the to-be-deleted list are 

copied to the clipboard. This information can then be pasted to a 

screen or to a file. 

324 6875 9497–003



Station Search With Empty Copy Text Causes Run-Time Error 381 

SYMPTOMS: 

Select 'Station Search' from the Options Menu selection. Click on 

'Copy Selected Text' when the listbox is empty. COMSCenter faults 

with "Run-time error '381': Invalid property array index". 


A new command button called 'Copy All Text' has been added in 

addition to the 'Copy Selected Text' command button. When clicked, 

this button copies all text in the listbox to the clipboard. 

Now, when either the 'Copy Selected Text' or the 'Copy All Text' 

command button is clicked, a message is displayed at the bottom 

of the form indicating that the desired action has occurred. If 

either button is pushed while the listbox is empty, a message is 

displayed indicating that no text was copied. 

Also, in order to be consistent with the date format in the results 

listbox, the Search Data format has been changed from the format of 

mm/dd/yy to yy/mm/dd. The field has been highlighted to emphasize 

the change. 


Station Search With Empty Copy Text Causes Run-Time Error 381 

SYMPTOMS: 

Select 'Station Search' from the Options Menu selection. Click on 

'Copy Selected Text' when the listbox is empty. COMSCenter faults 

with "Run-time error '381': Invalid property array index". 


A new command button called 'Copy All Text' has been added in 

addition to the 'Copy Selected Text' command button. When clicked, 

this button copies all text in the listbox to the clipboard. 

Now, when either the 'Copy Selected Text' or the 'Copy All Text' 

command button is clicked, a message is displayed at the bottom 

of the form indicating that the desired action has occurred. If 

either button is pushed while the listbox is empty, a message is 

displayed indicating that no text was copied. 

Also, in order to be consistent with the date format in the results 

listbox, the Search Data format has been changed from the format of 

mm/dd/yy to yy/mm/dd. The field has been highlighted to emphasize 

the change. 

6875 9497–003 325


NX/DBCENTER 

Component: DBCSERVICES PRI-11456014 

Database Operations Center Does Not Create Log File for Active 

NX Server 

SYMPTOMS: 

The DBCSRVCS (Active NX Server) does not create the log file when the 

the access privelges for the the system32 directory in Windows directory 

does not permit 'write' privilege. 


Help Text 

In 'Log File Locations' the following paragraph exists: 

The log file for the DBCSrvcs.exe out-of-process server is created in 

the folder specified by the windir System Variable in the system32 

folder. The log file is created with the title 

DBCSrvcs---.log. 

When the log file is closed, a Save As dialog box enables you to save 

or change the default log file name, DBCSrvcs.log. 

The DBCSrvcs.log file is automatically saved in the Database Operations 

Center application folder, not in the folder where the file is created. 

Replace the above paragraph with the following paragraph: 

The log file for the DBCSrvcs.exe out-of-process server is created in 

the folder in which the DBCSrvcs,exe was installed. Typically this is in 

the Database Operations Center application folder. 

The log file is created with the title 

DBCSrvcs---.log. 

When the log file is closed, a Save As dialog box enables you to save 

or change the default log file name, DBCSrvcs.log. 

NX/EDIT 

Component: NXEDIT-CLIENT PRI-11484875 

Load XREF File Option Added Under Xrefs In The Popup Menu 

SYMPTOMS: 

The Xrefs menu has no item to load XREF files. This would be useful 

in the Xrefs editing window pop-up menu if XREF files are not 

loaded. 

326 6875 9497–003



A Load Xref Files option has been added to the Xrefs pop-up and 

drop-menu. If XREF files are already loaded, the option is 

Reload Xref Files. 


Add Startcase As Edit Menu Item 

SYMPTOMS: 

Programmer's Workbench can convert tokens to uppercase and 

lowercase, but cannot convert to start case. 


You can now convert text to start case by selecting the Startcase 

item from the Edit menu. Startcase conversion converts each word by 

capitalizing the first character and converting the remaining 

characters to lower case. If the word consists of all capital 

letters, it will not be converted. 

Add the following information about Startcase in the Programmer's 

Workbench for ClearPath MCP Help Manual (form # 8999 5732). 

In the "Changing Capitalization" topic of the "Handle Text" topic 

of the "Tasks: How Do I ..." section, add "Startcase" as a third 

option. Ctrl+T is the keyboard short cut for Startcase. Add a note at 

the end of this page as: 

Startcase conversion converts each word by capitalizing the 

first character and converting the remaining characters to 

lower case. If the word consists of all capital letters, it is 

not changed. 

In the "Keyboard Shortcuts" topic, add a new row to the "Changing 

Capitalization" table: 

To ... Press ... 

Change test to start case Ctrl+T 


Recently Listed Files As File Menu Item 

SYMPTOMS: 

Programmer's Workbench doesn't have option to open recently listed 

files. 


Programmer's Workbench now supports a most recently used list for 

listed files. The last 10 files to be listed are saved, and can be 

re-selected for listing from the most recently used list. 

6875 9497–003 327


Add the following information about recently listed files in the 

Programmer's Workbench for ClearPath MCP Help Manual 

(form # 8999 5732). 

In the "List a File" topic of the "Work With Secondary Files" topic 

of "Tasks: How Do I ..." section, add the following before 

"More Information" 

Opening Recently Listed Files 

To open the most recently listed files 

1. From the File menu, select Recently Listed Files. 

A menu displays a list of the most recently listed files. 

2. Choose the file that you want to open. 

If the choosen file is unavailable, an error message is displayed 

and the file entry is removed from the list. 


Accesscode Password Must Be All Uppercase 

SYMPTOMS: 

Programmer's Workbench cannot login when an accesscode password 

contains lowercase or special characters. 


Programmer's Workbench now allows accesscode passwords to contain 

lowercase and special characters. Such a password must be entered in 

double quotes, unless the security option CASESENSITIVEPW option is 

set. If the option is set, the password must use the same case as the 

MCP accesscode password, and double quotes are optional. 

Add the a new topic "Passwords" under "Tasks: How do I..." in 

"Programmer's Workbench for ClearPath MCP Help Manual" 

(form # 8999 5732). 

Under the new topic "Passwords" add the following: 

Usercode and accesscode passwords are handled differently by 

Programmer's Workbench, especially with the handling of passwords 

containing lowercase and special characters. A usercode password 

must never by enclosed in double quotes, whereas an accesscode may 

be. The requirement for double quotes depends on the setting of 

the system security option CASESENSITIVEPW. If this option is set 

the "Connect To ..." dialog box will include the phrase "Passwords 

are case-sensitive". 

328 6875 9497–003


If CASESENSITIVEPW is reset: 

* Usercode passwords are treated in a case-sensitive manner, 

except that a password that contains only uppercase alphabetic 

characters and numbers can be entered without regard to case 

* Accesscode passwords are upcased unless they are entered in 

double quotes 

If CASESENSITIVEPW is SET: 

* Usercode passwords are treated in a case-sensitive manner and 

must match the case of the MCP password 

* Accesscode passwords are treated in a case-sensitive manner 

regardless of whether or not they are entered in double quotes 

Component: NXEDITSUPPORT PRI-11438784 

Support Connect as Logged On User 

SYMPTOMS: 

Programmer's Workbench cannot use Windows Credentials for log on. 


Programmer's Workbench can now use your Windows credentials when 

logging on to an MCP server. Your Windows credentials can be used if 

the password for the Windows username is the same as the password for 

the MCP usercode. The usercode used can be the same as the username, 

or the local alias of a remoteuser entry. 

In the Programmer's Workbench for Clear Path MCP Installation and 

Operations Guide (form # 8808 0049), add a new topic at the end of 

the "What is Programmer's Workbench?" section. 

Using Authentication Support 

Authentication support allows you to automatically log on using your 

Windows credentials. To use your Windows credentials, you need to 

* Create an MCP usercode with the same password as the password of 

the Windows username. 

* If the MCP usercode is different from the Windows username, 

create a remoteuser alias for host NXSERVICES. 

6875 9497–003 329


NX/OPCENTER 

Component: CLIENT PRI-11424651 

Maximum Number Of Fields For A View Is Not Documented 

SYMPTOMS: 

In Active View Definition --> Fields tab, the maximum number of 

Selected Fields is limited to ten and is not documented. 


The below mentioned NOTE should be added to Operations Center Help 

(.chm) file in, 

1. Menus -> File Menu -> "Open Dialog Box" link page 

2. Views -> Tabs Used to Control How Views Display -> Fields Tab -> 

"Add a field" section 


"Example 1" 


"Example 2" 

NOTE: Views with more than 10 fields cannot be opened by versions of 

Operations Center prior to 53.1 


Display And RSVP Message Appears On Every View Definition 

SYMPTOMS: 

"Show Last Display Message" and "Show RSVP Message" appears on every 

view definition. However, "Show Last Display Message" is only valid 

for Active and Waiting entries, Libraries, Databases and Messages. 

"Show RSVP Message" is only valid for Waiting entries, Libraries and 

Databases. 


You can no longer select "RSVP" messages for the Active View 

Definition. 

You can no longer select "DISPLAY" and "RSVP" messages for 

Completed and Scheduled, Messages, Disks, Tapes, Compact Discs, 

and Printers View Definitions. 

The Show Last Display Message and Show RSVP Message selection 

options will be ignored when opening a saved view where the selection 

options were set for views that no longer support those options. 

330 6875 9497–003

NX/SERVICES 

Component: ADMIN-CLIENT PRI-11487211 

Admincenter Client Truncates Long Share Names 


SYMPTOMS: 

Long share names do not entirely work properly. Browsing shares 

e.g. start - run - \\trprogd Will truncate names at 13 characters. 

Browsing into shares using these truncated names does not work. 


Update the following three documents. 

1. Client Access Services Administration Guide 

Configuration File Attributes 

Share conventions 

Share Name 

(a) Replace the following statement 

Share names begin with a letter or underscore (_), followed 

by up to 11 characters that may be letters, numbers, 

underscores, or dollar signs ($). 

As 

Share names begin with a letter or underscore (_), followed 

by characters that may be letters, numbers, underscores, or 

dollar signs ($). 

(b) Delete the following statement. 

Some workstations can only access shares with names of no 

more than 8 characters. 

2. Client Access Services User Guide 

Connecting to client Access Services 

Connecting to an MCP Share 

Replace the following statement 

is the shared resource you want to access. It 

can be 1 to 12 characters in length. 

As 

is the shared resource you want to access. 

3. Administration center help 

Getting Started 

Toolbar 

Create or Modify Resources 

Click on +more button 

Create or modify 

Tips for Creating a New Share 

6875 9497–003 331


Replace the following statement 

Share names may begin with a letter or underscore ( _ ), 

followed by up to 7 characters which may be letters, 

numbers, underscores, or dollar signs ($). (You may use 

more than 8 characters, but such shares are not recognized 

by some DOS redirectors.) 

As 

Share names may begin with a letter or underscore ( _ ), 

followed by characters which may be letters, numbers, 

underscores, or dollar signs ($). 

Component: LAUNCHER PRI-11495460 

Procedure To Run Launcher As An Application At System Boot 

SYMPTOMS: 

In order to start the Launcher application, users typically need to 

log on to the system. However, the Launcher application can be 

started when the system comes up and before the users log on. This 

can be achieved by using startup scripts that can be managed by the 

Windows Group Policy snap in. 


System Software Utilities Operations Reference Manual (86000395-513) 

PCDRIVER Utility 

Launcher 

After the topic Launcher Parameters, please add the following: 

Running Launcher at System Boot 

This method causes Launcher to run when the Windows system starts up 

without requiring a user to log onto the system. This method is 

useful for certain types of automated processing, but does not 

support user interaction with programs run by Launcher. 

This method uses a startup script managed by the Windows Group policy 

snap-in as described at http://support.microsoft.com/kb/198642. 

Here are the steps to follow. 

Open the Group Policy snap in by typing "gpedit.msc" in the Start-> 

Run dialog box. 

Choose Local Computer Policy->Computer Configuration-> 

Windows Settings->Scripts(Startup/Shutdown) 

Double click "Startup" in the details pane under the Scripts tab 

Click Add. 

332 6875 9497–003


In the "Add a Script" dialog box, give the path of the launcher.exe 

in the "Script Name" 

Example: "C:\Program Files\Unisys\MCP\Launcher\Launcher.exe" 

for the "Script Name" 

Enter the parameters that you need to supply to the Launcher.exe in 

the "Script Parameters" textbox. 

Example: 127.0.0.1 

Click OK to save in the "Add a Script" dialog box. 

Click OK to save in the "Scripts" tab. 

In the Group Policy Snap in window, under Computer Configuration-> 

Administrative templates-> System -> Scripts, there is an option 

called "Maximum wait time for Group Policy scripts", use 0 for 

infinite wait timeout. 

Also in this location turn on "Run startup scripts asynchronously" 

Exit the Group Policy program. Restart the system. 

Using this method, the Launcher dialog and launched application 

windows are often not visible; they may, depending on the version 

of Windows, be visible when no one is logged on or when the 

computer is locked. Launcher and launched applications are 

visible using the Windows task manager interface. 

-------------------------------------------------------------------- 

| Operating | User Logon | User Locked | User Logged | 

| System | Screen | State | On | 

-------------------------------------------------------------------| 

| | | | | 

| Windows XP | Visible | Visible | Invisible | 

| and 2003 | | | | 

|------------------------------------------------------------------| 

| | | | | 

|Windows Vista| Invisible | Invisible | Invisible | 

| and 2008 | | | | 

-------------------------------------------------------------------- 

| | | | | 

| Windows 7 | Invisible | Invisible | Invisible | 

| and 2008 R2 | | | | 

-------------------------------------------------------------------- 

Visibility of Launcher and Launched Application Windows 

6875 9497–003 333


Component: LAUNCHER PRI-11538304 

Procedure To Run Launcher As An Application At System Boot 

SYMPTOMS: 

In order to start the Launcher application, users typically need to 

log on to the system. However, the Launcher application can be 

started when the system comes up and before the users log on. This 

can be achieved by using startup scripts that can be managed by the 

Windows Group Policy snap in. 


System Software Utilities Operations Reference Manual (86000395-513) 

PCDRIVER Utility 

Launcher 

After the topic Launcher Parameters, please add the following: 

Running Launcher at System Boot 

This method causes Launcher to run when the Windows system starts up 

without requiring a user to log onto the system. This method is 

useful for certain types of automated processing, but does not 

support user interaction with programs run by Launcher. 

This method uses a startup script managed by the Windows Group policy 

snap-in as described at http://support.microsoft.com/kb/198642. 

Here are the steps to follow. 

Open the Group Policy snap in by typing "gpedit.msc" in the Start-> 

Run dialog box. 

Choose Local Computer Policy->Computer Configuration-> 

Windows Settings->Scripts(Startup/Shutdown) 

Double click "Startup" in the details pane under the Scripts tab 

Click Add. 

In the "Add a Script" dialog box, give the path of the launcher.exe 

in the "Script Name" 

Example: "C:\Program Files\Unisys\MCP\Launcher\Launcher.exe" 

for the "Script Name" 

Enter the parameters that you need to supply to the Launcher.exe in 

the "Script Parameters" textbox. 

Example: 127.0.0.1 

Click OK to save in the "Add a Script" dialog box. 

Click OK to save in the "Scripts" tab. 

334 6875 9497–003


In the Group Policy Snap in window, under Computer Configuration-> 

Administrative templates-> System -> Scripts, there is an option 

called "Maximum wait time for Group Policy scripts", use 0 for 

infinite wait timeout. 

Also in this location turn on "Run startup scripts asynchronously" 

Exit the Group Policy program. Restart the system. 

Using this method, the Launcher dialog and launched application 

windows are often not visible; they may, depending on the version 

of Windows, be visible when no one is logged on or when the 

computer is locked. Launcher and launched applications are 

visible using the Windows task manager interface. 

-------------------------------------------------------------------- 

| Operating | User Logon | User Locked | User Logged | 

| System | Screen | State | On | 

-------------------------------------------------------------------| 

| | | | | 

| Windows XP | Visible | Visible | Invisible | 

| and 2003 | | | | 

|------------------------------------------------------------------| 

| | | | | 

|Windows Vista| Invisible | Invisible | Invisible | 

| and 2008 | | | | 

-------------------------------------------------------------------- 

| | | | | 

| Windows 7 | Invisible | Invisible | Invisible | 

| and 2008 R2 | | | | 

-------------------------------------------------------------------- 

Visibility of Launcher and Launched Application Windows 

Component: MCP-NEIGHBORHOOD PRI-11492398 


SYMPTOMS: 






MCP Neighborhood Help (82145442) 

Introduction to the MCP Neighborhood Section. Add the following 

paragraph after the first sentence: 

By default, the products that use MCP Neighborhood install a 32-bit 



6875 9497–003 335








32-bit applications (such as SecurityCenter) use the 32-bit version, 


version. 


MCP Neighborhood Icon Is Visible Under Network Node Of Win7 

Explorer 

SYMPTOMS: 

On Windows Server 2008 R2 and later versions, MCP Neighborhood icon 

does not appear under "Desktop" node in the left pane of Windows 

Explorer. 


In MCP Neighborhood Help (82145442-000): 

What's New 

Please remove current text (it is for the MCP 12.0 release) and 

replace with "The Windows Server 2008 R2 and Windows 7 platforms 

are now supported. On these platforms, MCP Neighborhood has been 

placed in the "Network" node of Windows Explorer." 

Using MCP Neighborhood 

Add the following Note: 

Note: On Windows Server 2008 R2 and later versions, MCP servers 

are presented under the "MCP Neighborhood" icon on your desktop 

and in "Network" node of Windows Explorer. 


MCP Neighborhood Icon Is Visible Under Network Node Of Win7 

Explorer 

SYMPTOMS: 

On Windows Server 2008 R2 and later versions, MCP Neighborhood icon 

does not appear under "Desktop" node in the left pane of Windows 

Explorer. 

336 6875 9497–003


In MCP Neighborhood Help (82145442-000): 

What's New 


Please remove current text (it is for the MCP 12.0 release) and 

replace with "The Windows Server 2008 R2 and Windows 7 platforms 

are now supported. On these platforms, MCP Neighborhood has been 

placed in the "Network" node of Windows Explorer." 

Using MCP Neighborhood 

Add the following Note: 

Note: On Windows Server 2008 R2 and later versions, MCP servers 

are presented under the "MCP Neighborhood" icon on your desktop 

and in "Network" node of Windows Explorer. 

Component: PCDRIVER PRI-11547729 

Share Names With Embedded Blanks Not Accessible 

SYMPTOMS: 

When the variant (i.e., \\\) 

is used to access a share and the share name includes 

embedded blanks, the PCDDRIVER fails to access the share properly. 


Please update the System Software Utilities Operations 

Reference Manual (8600 0460-513) as follows: 

Under Section 22 PCDRIVER Utility, 

Running the PC Driver Utility 

Replace the description of the with the 

following: 

A Microsoft Networking share designation of the form 

\\\ 

This program will use the MCP REDIRECTOR feature to locate and 

communicate with a PC, which must have Microsoft Networking 

server functionality enabled. Note, if the target share name 

includes embedded blanks, the component 

must be enclosed in quotes. The following commands are not 

available when the PC is specified this way: RUN, LOCKEDRUN, 

LOCK, and UNLOCK. 

6875 9497–003 337


Component: PCDRIVER PRI-11547753 

Share Names With Embedded Blanks Not Accessible 

SYMPTOMS: 

When the variant (i.e., \\\) 

is used to access a share and the share name includes 

embedded blanks, the PCDDRIVER fails to access the share properly. 


Please update the System Software Utilities Operations 

Reference Manual (8600 0460-513) as follows: 

OLEDB 

Under Section 22 PCDRIVER Utility, 

Running the PC Driver Utility 

Replace the description of the with the 

following: 

A Microsoft Networking share designation of the form 

\\\ 

This program will use the MCP REDIRECTOR feature to locate and 

communicate with a PC, which must have Microsoft Networking 

server functionality enabled. Note, if the target share name 

includes embedded blanks, the component 

must be enclosed in quotes. The following commands are not 

available when the PC is specified this way: RUN, LOCKEDRUN, 

LOCK, and UNLOCK. 

Component: OLEDBPROVIDER PRI-11591027 

Accented characters in EBCDIC database 

SYMPTOMS: 

A DMSII database whose coded character set (CCS) is 

EBCDIC and whose CCSVersion is ASERIESNATIVE contains 

an ALPHA item. 

One or more characters in the ALPHA item are "accented" 

characters: accented characters include a diacritical 

mark, such as an umlaut or an accute accent. 

The accented characters are not translated correctly 

338 6875 9497–003

when the Ole DB Provider is used to retrieve the item 

using either of the following: 

- Visual C++ with an accessor (i.e., a binding) whose 

wType is DBTYPE_BSTR 

- a Visual Basic string 

For example, an uppercase I with accute accent may 

appear to be translated to a NULL. In an Ole DB 

Provider trace file, the character may appear to be 

translated to the question mark symbol (?). 


A new character set (LATIN1ISOASEBCDIC) is added to 

the character set designation in OLE DB Schema 

Utility to specify that the default ASCII/EBCDIC 

translation was performed on data stored in a DMSII 

database or MCP file, and the source ASCII character 

set was ISO 8859-1 (Latin 1 Western European). 

Help text affected: 

In Help/Tasks/Editing Coded Character Sets, add 

the following character set to the end of the 

character set list and the note that 

follows the list. 

LATIN1ISOASEBCDIC 

Note: LATIN1ISOASEBCDIC should only be used where 

ISO 8859-1 data was transferred to the MCP via 

methods that use the full ASCII/EBCDIC translation 

(e.g., FTP, terminal emulator) instead of any method 

that uses LATIN1EBCDIC translation (e.g., 

ODBC/OLE DB/JDBC). 

Component: OLEDBPROVIDER PRI-11591043 

Accented characters in EBCDIC database 

SYMPTOMS: 

A DMSII database whose coded character set (CCS) is 

EBCDIC and whose CCSVersion is ASERIESNATIVE contains 

an ALPHA item. 

One or more characters in the ALPHA item are "accented" 

characters: accented characters include a diacritical 

mark, such as an umlaut or an accute accent. 

The accented characters are not translated correctly 

when the Ole DB Provider is used to retrieve the item 

using either of the following: 


6875 9497–003 339


- Visual C++ with an accessor (i.e., a binding) whose 

wType is DBTYPE_BSTR 

- a Visual Basic string 

For example, an uppercase I with accute accent may 

appear to be translated to a NULL. In an Ole DB 

Provider trace file, the character may appear to be 

translated to the question mark symbol (?). 


A new character set (LATIN1ISOASEBCDIC) is added to 

the character set designation in OLE DB Schema 

Utility to specify that the default ASCII/EBCDIC 

translation was performed on data stored in a DMSII 

database or MCP file, and the source ASCII character 

set was ISO 8859-1 (Latin 1 Western European). 

PASCAL 


In Help/Tasks/Editing Coded Character Sets, add 

the following character set to the end of the 

character set list and the note that 

follows the list. 

LATIN1ISOASEBCDIC 

Note: LATIN1ISOASEBCDIC should only be used where 

ISO 8859-1 data was transferred to the MCP via 

methods that use the full ASCII/EBCDIC translation 

(e.g., FTP, terminal emulator) instead of any method 

that uses LATIN1EBCDIC translation (e.g., 

ODBC/OLE DB/JDBC). 

Component: PASCAL PRI-11433901 

Fix Heap OVERFLOW Result To Be 29, not 2 

SYMPTOMS: 

When separate heaps are not used (usually because $HEAPSEPARATE is 

not set), the result of a NEW or MARK statement that caused a heap 

overflow was 2. 

When separate heaps are used, the result is 29. 

HEAPRES(OVERFLOW) returns 29. 


For consistency purposes, 

when separate heaps are not used (usually because $HEAPSEPARATE is 


340 6875 9497–003


overflow is being changed from 2 to 29 in MCP 13.0 (SSR 54.1). 

Prior to MCP 13.0 (SSR 54.1), 

if your programs currently compare against a literal 2 or a 

HEAPRES(OVERFLOW) for a heap overflow condition, you should change 

it to compare the returned value against both 2 and 

HEAPRES(OVERFLOW). If the returned value is either 2 or 

HEAPRES(OVERFLOW) then treat it as a heap overflow condition. 

In MCP 13.0 (SSR 54.1) and later, 

if your programs currently compare against a literal 2, you should 

change it to compare against HEAPRES(OVERFLOW). 


Fix Heap OVERFLOW Result To Be 29, not 2 

SYMPTOMS: 

When separate heaps are not used (usually because $HEAPSEPARATE is 


overflow was 2. 

When separate heaps are used, the result is 29. 

HEAPRES(OVERFLOW) returns 29. 


For consistency purposes, 

when separate heaps are not used (usually because $HEAPSEPARATE is 


overflow is being changed from 2 to 29 in MCP 13.0 (SSR 54.1). 

Prior to MCP 13.0 (SSR 54.1), 

if your programs currently compare against a literal 2 or a 

HEAPRES(OVERFLOW) for a heap overflow condition, you should change 

it to compare the returned value against both 2 and 

HEAPRES(OVERFLOW). If the returned value is either 2 or 

HEAPRES(OVERFLOW) then treat it as a heap overflow condition. 

In MCP 13.0 (SSR 54.1) and later, 

if your programs currently compare against a literal 2, you should 

change it to compare against HEAPRES(OVERFLOW). 

6875 9497–003 341



Increase Maximum Value of $HEAPSIZE 

SYMPTOMS: 

Setting a value of $HEAPSIZE above 6291450 bytes causes the warning: 

THE HEAPSIZE OPTION HAS BEEN SET TO THE MAXIMUM VALUE OF 

6,291,450 BYTES. 


The HEAPSIZE compiler control option may now be set to a value as 

high as 805,306,362 bytes. 

In the Pascal Programming Reference Manual Volume 1: Basic 

Implementation (8600 0080-101), Page 16-19: 

Under the HEAPSIZE option, after the sentence that begins "If the 

value of the HEAPSIZE option is less ....", add the following 

sentence: "If the value of the HEAPSIZE option is greater than 

805306362, that value is ignored and the value 805306362 is assumed." 


No Bounds Checking On Parameters 

SYMPTOMS: 

Bounds checking is not performed on passed set parameters. 


Range-checking is not performed on parameters. 

PDIR 

In the Pascal Programming Reference Manual Volume 1 Basic 

Implementation (8600 0080-102); Section 16. Compiling Your Program; 

Using Compiler Control Records; Syntax for Compiler Control Options; 

BOUNDS Option; add the following sentence after the first sentence in 

the explanation: 

Range-checking is not performed on parameters. 

Component: PDIR PRI-11436234 

Return Information Through TASKSTRING Attribute 

SYMPTOMS: 

It is hard to use PDIR and PMIX to return information to a WFL job. 

342 6875 9497–003



You can now use the TASKSTRING keyword as an output option in PDIR 

and PMIX. If the TASKSTRING keyword is specified, PDIR and PMIX 

will return attribute information in the TASKSTRING task attribute. 

Each non-empty attribute value is reported, separated by semicolons. 

A maximum of 254 characters will be reported. 

The following information will be added to the PDIR Utility and PMIX 

Utility section of the System Software Utilities Operations 

Reference Manual (form # 8600 0460): 

The TASKSTRING keyword is now available as an alternative : 

---- TASKSTRING ( --- --- ) ----- 

If the TASKSTRING keyword is specified, a SHOW clause is not 

allowed; however, both SELECT and SORT are allowed. 

If more than one attribute value is reported, the values are 

separated by semicolons; empty attribute values are suppressed. 

If more than 254 characters of attribute values are generated, the 

last three characters of the TASKSTRING attribute are replaced with 

"...", and SW5 is set to indicate that the TASKSTRING has been 

truncated. 

Component: PDIR PRI-11476775 

Allow Multiple Attributes in TASKSTRING List 

SYMPTOMS: 

Only one attribute can be reported on when using the TASKSTRING 

output option. 

When running PDIR in batch mode, error messages such as 

No files were found 

cannot be suppressed. 


You can now specify more than one attribute in the TASKSTRING 

output list. If more than one attribute is listed, the TASKSTRING 

task attribute will be filled with attribute values for all objects 

where at least one of the attributes has a value. Each attribute 

is separated by a comma (,) and each object is separated by 

a semi-colon (;). 

6875 9497–003 343


The TASKSTRING keyword in is now defined as: 

---- TASKSTRING ( --- --- ) ----- 

where is defined as: 

PRINTS 

Component: DEPCON PRI-11580521 

Configure OPEN_TRY_COUNT for Virtual Server 


SYMPTOMS: 

Implement OPEN_TRY_COUNT to specify the maximum number of open 

attempts for the Virtual Server. 


Table 2-1 of the Enterprise Output Manager for ClearPath OS 2200 and 

ClearPath MCP Configuration and Operations Guide (form 7850 4362-006) 

needs to be updated by adding the following entry to the table: 

OPEN_TRY_COUNT 

Specifies the maximum number of attempts to open the destination, 

including both primary and alternate (if any), before abandoning the 

request and making it an exception. The maximum (and default) value 

is 10; the minimum value is 1. Applies to Virtual Server only. 

Component: DEPCON PRI-11580548 

Configure OPEN_TRY_COUNT for Virtual Server 

SYMPTOMS: 

Implement OPEN_TRY_COUNT to specify the maximum number of open 

attempts for the Virtual Server. 


Table 2-1 of the Enterprise Output Manager for ClearPath OS 2200 and 

ClearPath MCP Configuration and Operations Guide (form 7850 4362-006) 

needs to be updated by adding the following entry to the table: 

OPEN_TRY_COUNT 

Specifies the maximum number of attempts to open the destination, 

including both primary and alternate (if any), before abandoning the 

request and making it an exception. The maximum (and default) value 

is 10; the minimum value is 1. Applies to Virtual Server only. 

6875 9497–003 345


Component: PRINTDRIVERS PRI-11484042 

Allow Suppression of Form Feed After File is Printed 

SYMPTOMS: 

A form feed is generally emitted after each file in a print request 

is printed. For an RTF devices, this causes a wasted sheet of paper. 

We have accepted an NFS to permit this behavior to be suppressed at 

the device level. 


The device characteristic NOFORMFEED or NOFF can be configured on a 

virtual server or IO Handler, and negated with a minus sign. It will 

cause peripheral devices and virtual devices to not emit a page skip 

at the end of each file being printed. 


Implement Test IOHandler 


Devices may now be configured using and IOHandler called TEST. You 

should only use this IOHandler when instructed to by Unisys support. 


Allow Background Image For Generated HTML Document 

SYMPTOMS: 

A customer using the HTML driver of the Print System has been 

manually editing the generated HTML document in order to specify a 

background image for the body of the document. The customer 

submitted an NFS requesting that there be some method of doing this 

action automatically; we accepted the NFS. 


The HTML driver used with the PC, the DISKSHARE, or the STREAMFILE 

I/O handler can cause a background image to appear on the generated 

output document by specifying a PC-resident file name in the PAGECOMP 

applied to the file being printed. This is done by specifying FORM 

BACKGROUND in the Pagecomp. 

The form name may not include an ON clause or it will be 

ignored. 

346 6875 9497–003


The form name may be specified either as an absolute or a relative 

file name: 

absolute: FORM BACKGROUND = 'c:\permanent images\greenbar.jpg' 

Note that the entirety of the form name is within single quotes due 

to the several special characters. The system must be running with 

the LONGFILENAME sysops option Set in order to deal with this name, 

as it exceeds 17 characters. 

relative: FORM BACKGROUND = joe/pictures/'corporate.jpg' 

In this example, if the printer was configured to send documents to 

a directory called EXAMPLE, then the form would be expected to be in 

EXAMPLE\joe\pictures\corporate.jpg. 


Implement USEREQUESTNAME option 

SYMPTOMS: 

New Feature. 


The MCPPRT IOHANDLER parameter now supports a new option 

USEREQUESTNAME. When this option is set true the print jobs 

created under Windows will have the HOSTNAME and print request 

name included in the job name. 

This change also introduces HOSTNAME as a synonym for the existing 

DOMAIN parameter, so the following syntax would be allowed: 

PS CONFIG MYPRT IOHANDLER=MCPPRT(HOSTNAME=PRINTERHOST USEREQUESTNAME) 


Implement MYIPADDRESS option in MCPPRT and 

TCPDIRECTPRINTER 

SYMPTOMS: 

New Feature Request. 



MYIPADDRESS. When this option is set to a valid host IP address 

the MYIPADDRESS of the port file used to send requests to the 

PC component will be specified. This is intended to allow the 

6875 9497–003 347


system administrator to control which adapter is used. For example 

one might enter: 

PS CONFIG MYPRT IOHPARAM=(HOSTNAME=PRINTERHOST MYIPADDRESS=10.1.1.1) 

This change implements NFS 91329226. 


Implement REQUIRESTSTATUS option in MCPPRT 

SYMPTOMS: 

New feature. 



REQUIRESTATUS. This option can be set to values IDLE or CANPRINT 

to cause the MCPPRT code running on the PC to verify the status 

of the printer as reported by Windows. Setting CANPRINT requires 

the printer not return any status except "busy" or "printing" when 

queried and setting IDLE requires the printer to return no errors 

when queried. Beware, many printers do not correctly report their 

state, the a paused printer seems always to be detected. For example 

one might enter: 

PS CONFIG MYPRT IOHPARAM=(HOSTNAME=PRINTERHOST REQUIRESTATUS=IDLE) 

REQUIRESTATUS can be abbreviated RS. 

If REQUIRESTATUS is not set, or the PC component is an earlier 

version than 5.4.1 the behaviour is as before and printer 

status is ignored. 


Allow STREAMFILE I/O Handler to Generate Read-only Output Files 

SYMPTOMS: 

We have accepted an NFS requesting that read-only files be generated 

from certain I/O Handler devices. The STREAMFILE I/O Handler, which 

allows creation of stream files on an MCP host, is one such I/O 

Handler. 


The STREAMFILE I/O Handler can now create read-only output files. 

This facility is enabled by adding the new keyword READONLY as part 

of the configured IOHPARAM (or parameter portion of the IOHANDLER) 

348 6875 9497–003


for the device. This keyword joins the existing DIRECTORY and FAMILY 

parameters recognized by STREAMFILE devices. 

If enabled, the generation of read-only files cannot be negated for 

individual files being printed on such a device. 


Allow STREAMFILE I/O Handler to Generate Read-only Output Files 

SYMPTOMS: 

We have accepted an NFS requesting that read-only files be generated 

from certain I/O Handler devices. The STREAMFILE I/O Handler, which 

allows creation of stream files on an MCP host, is one such I/O 

Handler. 


The STREAMFILE I/O Handler can now create read-only output files. 

This facility is enabled by adding the new keyword READONLY as part 

of the configured IOHPARAM (or parameter portion of the IOHANDLER) 

for the device. This keyword joins the existing DIRECTORY and FAMILY 

parameters recognized by STREAMFILE devices. 

If enabled, the generation of read-only files cannot be negated for 

individual files being printed on such a device. 



SYMPTOMS: 










6875 9497–003 349


Component: PRINTS PRI-11447198 

Expand Maximum Number of Requests from 28339 to 100000 

SYMPTOMS: 

The current request request limit is 28339. It needs to be 

increased since active sites sometimes approach or reach that limit. 


In Table 1-3 Print System Limits (page 1-25 of the Print System 

User's Guide) change the Print Requests limit from 28,339 to 100,000. 



SYMPTOMS: 







Allow Printing Of Files Exceeding 16777215 Lines 

SYMPTOMS: 

When a file exceeding 16777215 lines is printed, only the first N 

lines are delivered to the output device, where N is 

modulo 16777215. 


The Print System can now print files exceeding 16777215 lines. This 

was previously an undocumented limitation. Certain restrictions 

apply when printing lines beyond 16777215: 

a). Forward skip operations (PS SKIP + N 

work, but Backward skip operations will cause an irrecoverable 

I/O error exception. 

b). Requeue operations with checkpoint cannot be resumed; an 

irrecoverable I/O error will be reported. 

Note that these two restrictions are not applicable if the current 

printing position in the file does not exceed 16777215. 

350 6875 9497–003


Allow Printpartial With Files Exceeding 16777214 Lines 


SYMPTOMS: 

The PRINTPARTIAL file attribute cannot represent line or record 

values exceeding 16777214. 


The structure used to define Printpartial ranges in the TRINFO array 

uses 24 bit fields for the start and end values of individual 

Printpartial ranges. Consequently, given that the "all bits on" 

value is used for the special case of END, numbers exceeding 

16777214 cannot be represented in this structure. A small number 

of customers are printing files exceeding 16777214 lines. 

Consequently, it has become necessary to expand the documented 

Printpartial structure. The old structure with fields in word 18 of 

TRINFO will be retained for three releases, whereupon word 18 will 

be zeroed. The new structure resides in TRINFO word 48, and is 

quite similar to the old structure. But the Printpartial range or 

ranges indexed from word 48 are slightly different, using a word each 

for the start and the end of individual ranges. END is indicated by 

the low-order 39 bits being all set, this being the maximum integer 

value in ClearPath architecture. 

A new bit in the old word 18 will be set if any range value exceeds 

16777214. This means that the previous Printpartial structure is 

bogus and should not be used. User-written software that deals with 

the Printpartial structure should be altered to use the new 

structure as time and resources permit. 



SYMPTOMS: 










6875 9497–003 351



Add A New Aseries Info Attribute to Return DL BACKUP 

Familyname 

SYMPTOMS: 

We have accepted an NFS requesting that the current system DL BACKUP 

familyname be made available to Print Center. 


Attribute #50 in the System Properties Default scope (scope #104) is 

a string-valued attribute which returns the value of the DL BACKUP 

familyname. This attribute is enquiry-only; it may not be modified. 


Add A New Aseries Info Attribute to Return DL BACKUP 

Familyname 

SYMPTOMS: 

We have accepted an NFS requesting that the current system DL BACKUP 

familyname be made available to Print Center. 


Attribute #50 in the System Properties Default scope (scope #104) is 

a string-valued attribute which returns the value of the DL BACKUP 

familyname. This attribute is enquiry-only; it may not be modified. 



SYMPTOMS: 










352 6875 9497–003




SYMPTOMS: 












SYMPTOMS: 










Component: REPRINTS PRI-11447210 


SYMPTOMS: 






6875 9497–003 353


SAN-DATAMOVER 

Component: WINSERVICES PRI-11479529 

TCP/IP transfers from Windows to MCP are now supported. 

SYMPTOMS: 

SAN DataMover would only support TCP/IP transfers from MCP 

to Windows. 


The San DataMover windows service and the MCP DataMover support 

library were modified to copy files from Windows to MCP over 

a TCP/IP socket. 


SAN DATAMOVER SUPPORTS MCP TO WINDOWS TO WINDOWS 

VIA DISK AND TCP/IP 

SYMPTOMS: 

In order to move files from MCP to windows and then push the file 

out to a remote windows server, FTP was required. 

Many organizations desire to not be required to deploy a separate 

FTP server and endure the overhead of the FTP protocol to accomplish 

the goal of moving files to a remote Windows Server. 


The DISK_TCPIP connection type allows for data to be moved from 

MCP to a Windows system via a transfer volume followed by a TCP/IP 

transfer to a remote Windows system. The remote Windows 

system must also be running the same version of SAN DataMover as 

the Windows system utilizing the transfer volume. 

The TCPIP_TCPIP connection type allows for data to be moved from 

MCP to a Windows system via TCP/IP followed by another TCP/IP 

transfer to a remote Windows system. As is the case with the 

DISK_TCPIP connection, both Windows systems must be running the 

same version of SAN DataMover. 

Note that if a user desires to move the data from the MCP 

to a platform other than Windows, FTP will still be required. 

Here is an example of a valid connection definition to use 

MCP-WIN-WIN transfers: 

CONNECTION MCP_WIN_WIN ( 

354 6875 9497–003

) 


TYPE=DISK_TCPIP 

,TCP_PORT = 40567 

,FINAL_NET_NAME = 

,DMV_NET_NAME = 

,FINAL_OS_TYPE = WIN 

,FINAL_USER =



SAN DATAMOVER SUPPORTS SSL FILE TRANSFERS 


Secure Socket Layer (SSL) communication is available for 

communication between the SAN DataMover Windows Service and the 

the MCP, and between two SAN DataMover Windows Services executing 

DISK_TCPIP and TCPIP_TCPIP transfers. 

SAN DataMover SSL configuration is performed via the DataMover 

Administration (MMC) console via the SSL tab in the properties 

window. The fields in the SSL tab are as follows: 

SSL Port: 

To change the default port that SAN DataMover will use for 

secure communications, change this value. The default is 40568. 

Remember to set this value in the MCP's configuration file if 

if it is changed here. 

Certificate File 

SAN DataMover requires an RSA certificate signed by a Certificate 

Authority. Provide the location of the certificate file (.PEM 

format only). 

Private Key File 

Provide the private key file (.PEM format) that was used to create 

certificate. The Private key can be in the 

same file as the certificate. If this is the case, then provide 

the same file in both fields. 


DATAMOVER SUPPORTS SECURE FTP TRANSMISSIONS 


A new connection attribute, SECURE_PROTOCOL, has been implemented. 

To use FTPS, set SECURE_PROTOCOL for a given connection to FTPS. 

FTPS is FTP over Secure Socket Layer(SSL). It is different from 

SFTP, secure FTP over SSH. 

This patch implements FTPS only. 

356 6875 9497–003

SDASUPPORT 

Component: SDASUPPORT-NONDA PRI-11445951 

Allow Filtering On More Than One Usercode 


SYMPTOMS: 

When SYSTEM/IGSDASUPPORT is installed as the SDASUPPORT library, a 

user with direct read access to the log can use the UC or USERCODE 

LOGANALYZER option to limit the entries analyzed from the log to a 

specific usercode. 

However, it is not possible to specify a list of usercodes for which 

filtering is desired. 


The USERCODE (UC), ACCESSCODE (AC) and CHARGECODE (CC) LOGANALYZER 

options can now be followed by a list of identifiers. If more than 

one identifier is specified, the log will be filtered to show 

entries for all identifiers in the list. The special identifier 

"." is incompatible with a list (because it indicates that no 

filtering is desired). 

Modify the "Selection Options" topic of the "LOGANALYZER Options" 

topic of the "LOGANALYZER" section of the System Software Utilities 


Change the railroad diagram for the 

ACCESSCODE, CHARGECODE, and USERCODE bars to include a metatoken 

and to add a /1\ bridge at the beginning. 

The metatoken is defined as: 

+----------- , ------------+ 

| | 

----------+----


SECURITY 

Component: MAKEUSER PRI-11476210 


SYMPTOMS: 













================ 




For example, 














================ 



358 6875 9497–003
























Node Item 

1 Local alias 







Component: MAKEUSER PRI-11478883 

Interactive Output Scrolls Too Fast 

SYMPTOMS: 

If the output from a MAKEUSER command exceeds the number of lines on 

the terminal, output is overwritten. 


You can now use the PAGE control option to prevent MAKEUSER output 

from exceeding the page length of the terminal. 

6875 9497–003 359


Add the PAGE option to the description of Output Control Options 

in the Session Control Options section of the Security Administration 

Guide (form # 8600 0973). 

PAGE 

-- PAGE --------------------------------------------------| 

(Type: Boolean; Default: FALSE) 

Use the PAGE option to avoid MAKEUSER output that exceeds the 

page length overwriting previous input. If the PAGE option is 

TRUE, MAKEUSER will pause after (page length - 1) lines of 

output have been written. 

If you transmit STOP, output will be terminated. 

If you transmit MUTE, and the output is related to a COPY or 

ACCESS command, or input is being read from a disk file (as a 

result of a $INPUT command), the command will continue but 

output will suppressed until a new command is entered. 

Any other input resumes output. 

The PAGE option is only honored for interactive sessions; it is 

ignored otherwise. 

Component: MCPCRYPTOAPI PRI-11518702 

Fix Description Of McpCertGetX509EncodedCertificateChain 

SYMPTOMS: 

The description of the pCertificateChain output parameter of the 

McpCertGetX509EncodedCertificateChain interface is incomplete. 


The current description of the parameter is: 

pCertificateChain 

Output parameter. 

A pointer that points to the X509 encoded 

certificate chain. The user or service's 

certificate will be first, followed by the 

certificates of the issuing Certificate 

Authorities. 

The description of this parameter should be: 



A pointer that points to a 3-byte length 

field, followed by the X509 encoded 

certificate itself. The 3-byte length field 

contains the length of the certificate that 

360 6875 9497–003

immediately follows the length field, not 

including the length field itself. 

If more than one certificate is returned 

each certificate is preceded by a 3-byte 

length field containing its length. 

Normally, only one certificate is returned. 




SYMPTOMS: 











Authorities. 














6875 9497–003 361




SYMPTOMS: 











Authorities. 










SECURITYCENTER 






Implement export and import of IPsec policies 

SYMPTOMS: 

Files cannot be imported from an MCP server. Duplicate SPI numbers 

are not flagged. Memory leaks are present. 



SecurityCenter Help (4310 9263): 

362 6875 9497–003


"IPsec Policy" 

Please add "export" and "import" to the list of operations that 

can be done on IPsec policies (with links to the new topics below) 

"Exporting IPsec Policies" 

IPsec policies can be exported to a file. Under "Security Policy 

Management," right-click "IPsec Policies." Double-click on 

"Export IPsec Policies." A window titled "Export IPsec Policies" 

is presented. This window contains a list of the names of the 

current IPsec policies at this host. Each name is preceded by a 

check box. 

To export all policies, click the button labelled "Export All." 

To select individual policies, point to the check box before a 

policy name, and either click the mouse button or press the 

space bar. Do this for each policy to be selected, then click the 

button "Export Selected." 

A file open dialog is displayed. Specify the name and location 

of the export file, and click OK to save the file. 

NOTE: Export the IPsec keys, separately, using the Export 

function of the MCP Cryptographic Service Manager. 

In order to import IPsec policies, the IPsec keys used by 

those policies must be present on the importing host. 

This is particularly significant when the importing host 

is not the host on which the policy was created. 

In the case of automatically generated keys, it is not 

sufficient to create a key of the same name on another 

host, because the key contents would differ. The original 

key for a given policy must be installed at all hosts 

which use that policy. Manual key duplication is prone 

to error. The best way to guarantee correct keys is to 

export the IPsec keys whenever IPsec policies are 

exported, and to keep the key and policy files together. 

"Importing IPsec Policies" 

IPsec policies exported to a file can be imported at any MCP host. 

NOTE: IPsec keys from the originating host must be present before 

IPsec policies are imported. Before attempting to import 

policies, verify that IPsec keys used by those policies 

are present. If necessary, import the file of IPsec keys 

exported from the originating host. 

Refer to the note, below. 

If the IPsec keys are present, initiate policy import by 

right-clicking "IPsec Policies" under "Security Policy 

Management." Double-click on "Import IPsec Policies." The IPsec 

6875 9497–003 363


Policy wizard begins. The Create/Update IPsec Policies window is 

displayed. Click the Import button. 

A file open dialog appears. Select the name of the IPsec policy 

export file to use, and click OK. A window titled "Import IPsec 

Policies" is presented. This window contains a list of the names 

of the IPsec policies contained in the current export file. Each 

name is preceded by a check box. 

To import all policies, click the button labelled "Import All." 



space bar. (A visible check mark appears.) Do this for each 

policy to be selected, then click the button "Import Selected." 

The Create IPsec Policies window is displayed. Any errors found, 

such as duplicate names or SPI numbers, are displayed in 

individual messages. Take note of the policy names and errors 

shown. 

At this point, click Import to import another policy export 

file, or select any of the other actions. 

POLICIES IMPORTED FROM ANOTHER HOST MUST BE MODIFIED. At the 

least, the IP addresses and port numbers must be verified, 

and the local host's IP address entered. If the direction (In or 

Out) changes, the local and remote entries may need to be 

exchanged. Policies imported to the same host from which they 

were exported must still be verified. Any errors noted during 

the import must be corrected. 

Be sure to modify every policy which had an error. When Finish 

is clicked, an error in any policy causes all new policies to 

be discarded. 

When manual updates are complete, click Next to proceed to the 

IPsec Test wizard. When the Test Wizard is complete, the 

policies can be saved. 

NOTE: IPsec keys from the originating host must be present. 

If they are not already present, import the IPsec keys from 

the originating host. 










to error. 

364 6875 9497–003


The best way to guarantee correct keys is to export the 

IPsec keys whenever IPsec policies are exported, keep the 

key and policy files together, and import the keys at the 

new host before importing the policies. 



SYMPTOMS: 

Files cannot be imported from an MCP server. Duplicate SPI numbers 

are not flagged. Memory leaks are present. 













check box. 


















6875 9497–003 365
































shown. 












be discarded. 

366 6875 9497–003

















to error. 





Component: CRYPTOMANAGER PRI-11539017 

DNOTE for JAVA Stores feature in SecurityCenter (part of FN 

#1947). 

SYMPTOMS: 

Documentation DNOTE for Security Integration piece of MCP 13.0 

Feature #1947. 


Security Administration Guide (8600 0973): 

Section 9, page 9-2: 

In the paragraph "MCP Cryptographic Services Manager..." add the 

following sentence. 

"It also allows the security administrator to manage certificates and 

certificate stores for use with the Secure Java product." 


Security Center Help (4310 9263): (* denotes a new topic, ## shows 

a link). The overall structure should be: 

+ Trusted Stores 

Trusted Stores 

+ MCP Trusted Stores * 

MCP Trusted Stores * 

6875 9497–003 367


Create Store * 

Install Certificate Into Store * 

Delete Certificate * 

Delete Store * 

Export Store * 

+ JAVA Trusted Stores * 

JAVA Trusted Stores and Certificates * 

+ JAVA Trusted Store Operations * 

Create JAVA Trusted Store * 

Delete JAVA Trusted Store * 

View JAVA Trusted Store Properties * 

Synchronize JAVA Audit Database * 

Change Keystore Password * 

+ JAVA Certificate Operations * 

Create JAVA Certificate * 

Import JAVA Certificate * 

Export JAVA Certificate * 

Delete JAVA Certificate * 

Change JAVA Certificate Alias * 

View JAVA Certificate Properties * 

In the "MCP Cryptographic Services Manager" topic, please replace 

the 2nd and 3rd paragraphs with the following text: 

"This module allows the security administrator to create and 

manage the cryptographic keys for use with the ClearPath MCP 

environment. It also allows the security administrator to manage 

the trust environment for applications running on the ClearPath 

MCP environment. 

This module can be used to create and manage the asymmetric keys 

used for SSL and Tape Encryption, as well as the symmetric keys used 

for IPsec. For more detail, see the #Trusted Keys# topic). The 

security administrator can also use this module to manage the 

the certificate and certificate stores used by the ClearPath MCP 

environment. For more detail, see the #Trusted Stores# topic)." 

In the "Trusted Stores" topic, add this paragraph between the 1st 

and 2nd paragraph: 

This module supports two types of trusted certificate stores. 

* MCP Trusted Stores: These trusted stores are used by the MCP 

environment for validation of X.509 certificates used by the 

SSL protocol. 

* JAVA Trusted Stores: These trusted stores are used by the 

Secure Java product on the ClearPath MCP environment for 

validation of X.509 certificates. It provides a more 

convenient way of managing certificates and certificate stores. 

NEW TOPIC: MCP Trusted Stores 

MCP Trusted stores are used to validate X.509 certificates received 

from peers using the SSL or TLS protocol when using WebTS for 

ClearPath MCP, FTP, or a custom-protocol. By default, these 

protocols use the ROOT trusted store to validate certificates, but 

other stores can be created and configured for use. A security 

administrator can #create# a certificate store, #install# a 

certificate into the store, #delete# a certificate, #delete# the 

store, and #export# the store for use on another system. 

368 6875 9497–003


Importing a certificate store can be performed from the root node 

of MCP Cryptographic Services Manager. 

Also provide the following links. 

* #create# cross-references to "Create Store" 

* #install# cross-references to "Install Certificate Into Store" 

* #delete# cross-references to "Delete Certificate" 

* #delete# cross-references to "Delete Store" 

* #export# cross-references to "Export Store" 

NEW TOPIC: Create Store 

To create a new MCP trusted store, follow these steps. 

- Open the Cryptographic Services Manager, and then select the 

trusted store node. 

- Click on the icon or right-click and then select " 

"Create Store" pop-up menu. 

The "Create Trusted Store" will display. Fill in the following 

information. 

- Enter a store name in the "Enter a trusted store name" box. 

- Ensure that the checkbox "Is this a Java trusted store?" is not 

checked. 

- Hit OK button to create a MCP trusted store node. 

NEW TOPIC: Install Certificate Into Store 

To install a certificate into a MCP trusted store, right-click on 

the store and then select "Import Certificate Into Store" pop-up 

menu. A dialog box will be displayed to browse for the certificate 

file. Select the file which contains the certificate and hit OK. 

The certificate will be imported into the store. 

NEW TOPIC: Delete Certificate 

To delete a certificate from a certificate store, highlight the 

certificate in the result pane, and either select delete from the 

right-click menu, select the icon, or hit the Delete 

button. The certificate will be deleted from the store. 

NEW TOPIC: Delete Store 

To delete a MCP trusted store, highlight the trusted store in 

either the scope or result pane, and either select delete from 

select delete from the right-click menu, select the icon 

or hit Delete button. The trusted store will be deleted. 

NEW TOPIC: Export Store 

To transfer the entire contents of a trusted store to a file, 

select the trusted store and select Export Store from the right-click 

menu. After the warning dialog box is displayed, a dialog box will 

be shown to specify the filename for the certificate store. Browse to 

the directory and specify the filename to be used and hit the OK 

button. The contents of the store will be saved to this file. 

MCP Trusted Stores can also be exported from the main MCP 

Cryptographic Services Manager node through the Export function. 

NEW TOPIC: JAVA Trusted Stores and Certificates 

This module allows the security administrator to #create# a 

certificate store for Java. It also allows the security administrator 

6875 9497–003 369


to #delete# the store, #view# its properties, #change keystore 

password# and #synchronize# its audit database. For administration of 

Java certificates, the security administrator can #create# a 

certificate for use with Java. They may also #import# a Java 

Certificate into the keystore, #export# the Java Certificate from 

the Java keystore, #delete# the certificate, #view# its properties, 

and #change# the Java certificate alias. 


- #create# cross-references to "Create Java Trusted Store". 

- #delete# cross-references to "Delete Java Trusted Store". 

- #view# cross-references to "View Java Trusted Store Properties". 

- #change keystore password# cross-references to "Change Keystore 

Password". 

- #synchronize# cross-references to "Synchronize Java Audit 

Database". 

- #create #cross-references to "Create Java Certificate" 

- #import# cross-references to "Import Java Certificate" 

- #export# cross-references to "Export Java Certificate" 

- #delete# cross-references to "Delete Java Certificate" 

- #change# cross-references to "Change Java Certificate Alias" 

- #view #cross-references to "View Java Certificate Properties" 

NEW TOPIC: Create JAVA Trusted Store 

To create a new Java trusted store, follow these steps. 



- Click on the icon or right-click and then 

select "Create Store" pop-up menu. The "Create Trusted Store" 

will display. Fill in the following information. 


- Check the "Is this a Java trusted store?" checkbox. Note that 

this checkbox will be disabled if connecting the module to a 

level of Security Center that does not support the Java KeyTool 

feature. 

- Enter the keystore password in the "Enter keystore password" 

box. The password must be at least 6 characters. 

- Re-enter the keystore password in the "Re-enter keystore 

password". 

- Enter, select or browse a MCPJAVA JRE location in the "Enter, 

select or browse a MCP JRE location" drop-down box. The MCPJAVA 

JRE path must be valid and in this format: /DIR/JREn 

(where n is a number of MCPJAVA version, which must be 6 or 

greater). For example, JAVA6/DIR/JRE6. This MCP relative path 

is translated as *DIR/JRE6 on JAVA6. 

- Enter a keystore file name in the "Enter keystore file name" box 

- Hit OK button to create a Java trusted store node. 

NEW TOPIC: Delete Java Trusted Store 

To delete the Java Trusted Store, do the following steps. 

- Open the Crypto Services Manage, and then select the trusted 

store node. 

- Click on the icon or right-click and then select the 

"Delete" pop-up menu. The "confirm delete" pop-up dialog will 

display. Hit OK button to delete store. 

370 6875 9497–003


NEW TOPIC: View Java Trusted Store Properties 

To view the Java Trusted Store properties, click on the 

icon or right-click and then select the "Properties" pop-up menu. 

The properties dialog will display and show a full keystore path 

path (For example, *DIR/JRE6/LIB/SECURITY/JKSFILE on JAVA6). Note 

Note that the LIB/SECURITY is automatically added to the path 

because this is the storage where all Java security files reside. 

NEW TOPIC: Synchronize Java Audit Database 

The synchronization process is to keep the Java keystore in sync 

with Java audit database. To synchronize Java audit database, 

right-click and then select "Synchronize Java Audit Database" 

pop-up menu. 

The "Synchronize Java Audit Database" dialog will display. The 

progress bar in the "Synchronize Java Audit Database" dialog will 

indicate how far the process is being completed. The user can 

cancel the process by clicking on the Cancel button. Note that this 

will be disabled if there are no pending journal commands (database 

entries) in the Java audit database. 

NEW TOPIC: Change Keystore Password 

To change keystore password, click on the icon or 

right-click and then select "Change Java Keystore Password" pop-up 

menu. 

The "Change Keystore Password" dialog will display. Fill in the 

following information. 

- Enter the old password in the "Enter old password". 

- Enter a new password in the "Enter new password". 

- Confirm a new password by re-entering it in the "Confirm 

new password". 

- Hit OK button. 

NEW TOPIC: Create Java Certificate 

To create a Java certificate, click on the 

icon or right-click and then select "Create Java Certificate" from 

the pop-up menu. 

The "Create Java Certificate" dialog will display. Fill in the 


- Enter the certificate owner's information in the "Owner 

Information" section. 

- Enter number of days the certificate will be valid. 

- Enter the certificate alias name. It should be unique in the 

entire keystore. 

- Enter the password for this keystore. 


If no error message is displayed, the "Create Java Certificate" 

process is completed and the certificate is successfully added to 

the keystore. If server responds with a message saying "The re- 

quested command will be saved in the Java audit database", the 

"Create Java Certificate" process is completed but the certificate 

has not been successfully added to the keystore. It is saved in 

the Java audit database. The user can re-run the request later by 

executing the "Synchronize Java Audit Database" command. 

6875 9497–003 371


NEW TOPIC: Import Java Certificate 

To import a Java certificate, click on the 

icon or right-click and then select "Import Java Certificate" 

from the pop-up menu. 

The "Import Java Certificate" dialog will display. Fill in the 




- Enter or browse a certificate file name in the "Certificate 

File" box. The file extension is usually .cer, .crt or .cert. 

- Enter the keystore password. 


If no error message is displayed, the "Import Java Certificate" 




"Import Java Certificate" process is completed but the certificate 




NEW TOPIC: Export Java Certificate 

To export a Java certificate, click on the 

icon or right-click and then select the "Export Java Certificate" 


The "Export Java Certificate" dialog will display. Fill in the 


- Enter or browse an exported certificate file in the "Export 

certificate to file" box. Note that the exported file must be 

valid and in the local Windows machine. The file extension is 

usually .cer, .crt or .cert. 



NEW TOPIC: Delete Java Certificate 

To delete a Java certificate, click on the 

icon or right-click and then select the "Delete" from the pop-up 

menu. 

The "confirm delete" pop-up dialog will display. 

Hit OK button. 

If no error message is displayed, the "Delete Java Certificate" 

process is completed and the certificate is successfully deleted 

from the keystore. If server responds with a message saying "The 

requested command will be saved in the Java audit database", the 

"Delete Java Certificate" process is completed but the certificate 

has not been successfully deleted from the keystore. The operation 

has been saved in the Java audit database. The user can re-run the 

operation by executing the "Synchronize Java Audit Database" 

command. 

NEW TOPIC: Change Java Certificate Alias 

To change Java certificate alias, right-click and then select the 

"Rename". The name will be highlighted. Enter a new name for this 

certificate. Note that the name should be unique in the entire 

keystore. 

372 6875 9497–003


If no error message is displayed, the "Change Java Certificate 

Alias" process is completed and the certificate alias has been 

successfully changed. If the server responds with a message 

saying that "The requested command will be saved to the Java audit 

database", the "Change Java Certificate Alias" process is completed 

but the certificate alias has not been changed. The operation has 

been saved in the Java audit database. The user can re-run the 


command. 

NEW TOPIC: View Java Certificate Properties 

To view Java certificate properties, click on the icon 

or right-click and then select the "Properties" from the pop-up 

menu. 

The properties dialog will display and show the properties such as 

common name, issuer, version, serial number and fingerprints. 

Component: CRYPTOMANAGER PRI-11539033 

DNOTE for JAVA Stores feature in SecurityCenter (part of FN 

#1947). 

SYMPTOMS: 

Documentation DNOTE for Security Integration piece of MCP 13.0 

Feature #1947. 



Section 9, page 9-2: 

In the paragraph "MCP Cryptographic Services Manager..." add the 

following sentence. 

"It also allows the security administrator to manage certificates and 

certificate stores for use with the Secure Java product." 


Security Center Help (4310 9263): (* denotes a new topic, ## shows 

a link). The overall structure should be: 

+ Trusted Stores 

Trusted Stores 

+ MCP Trusted Stores * 

MCP Trusted Stores * 

Create Store * 

Install Certificate Into Store * 

Delete Certificate * 

Delete Store * 

Export Store * 

+ JAVA Trusted Stores * 

JAVA Trusted Stores and Certificates * 

+ JAVA Trusted Store Operations * 

Create JAVA Trusted Store * 

6875 9497–003 373


Delete JAVA Trusted Store * 

View JAVA Trusted Store Properties * 

Synchronize JAVA Audit Database * 

Change Keystore Password * 

+ JAVA Certificate Operations * 

Create JAVA Certificate * 

Import JAVA Certificate * 

Export JAVA Certificate * 

Delete JAVA Certificate * 

Change JAVA Certificate Alias * 

View JAVA Certificate Properties * 

In the "MCP Cryptographic Services Manager" topic, please replace 

the 2nd and 3rd paragraphs with the following text: 

"This module allows the security administrator to create and 

manage the cryptographic keys for use with the ClearPath MCP 

environment. It also allows the security administrator to manage 

the trust environment for applications running on the ClearPath 

MCP environment. 

This module can be used to create and manage the asymmetric keys 

used for SSL and Tape Encryption, as well as the symmetric keys used 

for IPsec. For more detail, see the #Trusted Keys# topic). The 

security administrator can also use this module to manage the 

the certificate and certificate stores used by the ClearPath MCP 

environment. For more detail, see the #Trusted Stores# topic)." 

In the "Trusted Stores" topic, add this paragraph between the 1st 

and 2nd paragraph: 

This module supports two types of trusted certificate stores. 

* MCP Trusted Stores: These trusted stores are used by the MCP 

environment for validation of X.509 certificates used by the 

SSL protocol. 

* JAVA Trusted Stores: These trusted stores are used by the 

Secure Java product on the ClearPath MCP environment for 

validation of X.509 certificates. It provides a more 

convenient way of managing certificates and certificate stores. 

NEW TOPIC: MCP Trusted Stores 

MCP Trusted stores are used to validate X.509 certificates received 

from peers using the SSL or TLS protocol when using WebTS for 

ClearPath MCP, FTP, or a custom-protocol. By default, these 

protocols use the ROOT trusted store to validate certificates, but 

other stores can be created and configured for use. A security 

administrator can #create# a certificate store, #install# a 

certificate into the store, #delete# a certificate, #delete# the 

store, and #export# the store for use on another system. 

Importing a certificate store can be performed from the root node 

of MCP Cryptographic Services Manager. 


* #create# cross-references to "Create Store" 

* #install# cross-references to "Install Certificate Into Store" 

* #delete# cross-references to "Delete Certificate" 

* #delete# cross-references to "Delete Store" 

* #export# cross-references to "Export Store" 

374 6875 9497–003


NEW TOPIC: Create Store 

To create a new MCP trusted store, follow these steps. 



- Click on the icon or right-click and then select " 

"Create Store" pop-up menu. 

The "Create Trusted Store" will display. Fill in the following 

information. 


- Ensure that the checkbox "Is this a Java trusted store?" is not 

checked. 

- Hit OK button to create a MCP trusted store node. 

NEW TOPIC: Install Certificate Into Store 

To install a certificate into a MCP trusted store, right-click on 

the store and then select "Import Certificate Into Store" pop-up 

menu. A dialog box will be displayed to browse for the certificate 

file. Select the file which contains the certificate and hit OK. 

The certificate will be imported into the store. 

NEW TOPIC: Delete Certificate 

To delete a certificate from a certificate store, highlight the 

certificate in the result pane, and either select delete from the 

right-click menu, select the icon, or hit the Delete 

button. The certificate will be deleted from the store. 

NEW TOPIC: Delete Store 

To delete a MCP trusted store, highlight the trusted store in 

either the scope or result pane, and either select delete from 

select delete from the right-click menu, select the icon 

or hit Delete button. The trusted store will be deleted. 

NEW TOPIC: Export Store 

To transfer the entire contents of a trusted store to a file, 

select the trusted store and select Export Store from the right-click 

menu. After the warning dialog box is displayed, a dialog box will 

be shown to specify the filename for the certificate store. Browse to 

the directory and specify the filename to be used and hit the OK 

button. The contents of the store will be saved to this file. 

MCP Trusted Stores can also be exported from the main MCP 

Cryptographic Services Manager node through the Export function. 

NEW TOPIC: JAVA Trusted Stores and Certificates 

This module allows the security administrator to #create# a 

certificate store for Java. It also allows the security administrator 

to #delete# the store, #view# its properties, #change keystore 

password# and #synchronize# its audit database. For administration of 

Java certificates, the security administrator can #create# a 

certificate for use with Java. They may also #import# a Java 

Certificate into the keystore, #export# the Java Certificate from 

the Java keystore, #delete# the certificate, #view# its properties, 

and #change# the Java certificate alias. 


6875 9497–003 375


- #create# cross-references to "Create Java Trusted Store". 

- #delete# cross-references to "Delete Java Trusted Store". 

- #view# cross-references to "View Java Trusted Store Properties". 

- #change keystore password# cross-references to "Change Keystore 

Password". 

- #synchronize# cross-references to "Synchronize Java Audit 

Database". 

- #create #cross-references to "Create Java Certificate" 

- #import# cross-references to "Import Java Certificate" 

- #export# cross-references to "Export Java Certificate" 

- #delete# cross-references to "Delete Java Certificate" 

- #change# cross-references to "Change Java Certificate Alias" 

- #view #cross-references to "View Java Certificate Properties" 

NEW TOPIC: Create JAVA Trusted Store 

To create a new Java trusted store, follow these steps. 



- Click on the icon or right-click and then 

select "Create Store" pop-up menu. The "Create Trusted Store" 

will display. Fill in the following information. 


- Check the "Is this a Java trusted store?" checkbox. Note that 

this checkbox will be disabled if connecting the module to a 

level of Security Center that does not support the Java KeyTool 

feature. 

- Enter the keystore password in the "Enter keystore password" 

box. The password must be at least 6 characters. 

- Re-enter the keystore password in the "Re-enter keystore 

password". 

- Enter, select or browse a MCPJAVA JRE location in the "Enter, 

select or browse a MCP JRE location" drop-down box. The MCPJAVA 

JRE path must be valid and in this format: /DIR/JREn 

(where n is a number of MCPJAVA version, which must be 6 or 

greater). For example, JAVA6/DIR/JRE6. This MCP relative path 

is translated as *DIR/JRE6 on JAVA6. 

- Enter a keystore file name in the "Enter keystore file name" box 

- Hit OK button to create a Java trusted store node. 

NEW TOPIC: Delete Java Trusted Store 

To delete the Java Trusted Store, do the following steps. 

- Open the Crypto Services Manage, and then select the trusted 

store node. 

- Click on the icon or right-click and then select the 

"Delete" pop-up menu. The "confirm delete" pop-up dialog will 

display. Hit OK button to delete store. 

NEW TOPIC: View Java Trusted Store Properties 

To view the Java Trusted Store properties, click on the 

icon or right-click and then select the "Properties" pop-up menu. 

The properties dialog will display and show a full keystore path 

path (For example, *DIR/JRE6/LIB/SECURITY/JKSFILE on JAVA6). Note 

Note that the LIB/SECURITY is automatically added to the path 

because this is the storage where all Java security files reside. 

376 6875 9497–003


NEW TOPIC: Synchronize Java Audit Database 

The synchronization process is to keep the Java keystore in sync 

with Java audit database. To synchronize Java audit database, 

right-click and then select "Synchronize Java Audit Database" 

pop-up menu. 

The "Synchronize Java Audit Database" dialog will display. The 

progress bar in the "Synchronize Java Audit Database" dialog will 

indicate how far the process is being completed. The user can 

cancel the process by clicking on the Cancel button. Note that this 

will be disabled if there are no pending journal commands (database 

entries) in the Java audit database. 

NEW TOPIC: Change Keystore Password 

To change keystore password, click on the icon or 

right-click and then select "Change Java Keystore Password" pop-up 

menu. 

The "Change Keystore Password" dialog will display. Fill in the 


- Enter the old password in the "Enter old password". 

- Enter a new password in the "Enter new password". 

- Confirm a new password by re-entering it in the "Confirm 

new password". 


NEW TOPIC: Create Java Certificate 

To create a Java certificate, click on the 

icon or right-click and then select "Create Java Certificate" from 

the pop-up menu. 

The "Create Java Certificate" dialog will display. Fill in the 


- Enter the certificate owner's information in the "Owner 

Information" section. 

- Enter number of days the certificate will be valid. 



- Enter the password for this keystore. 


If no error message is displayed, the "Create Java Certificate" 




"Create Java Certificate" process is completed but the certificate 




NEW TOPIC: Import Java Certificate 

To import a Java certificate, click on the 

icon or right-click and then select "Import Java Certificate" 


The "Import Java Certificate" dialog will display. Fill in the 




- Enter or browse a certificate file name in the "Certificate 

6875 9497–003 377


File" box. The file extension is usually .cer, .crt or .cert. 



If no error message is displayed, the "Import Java Certificate" 




"Import Java Certificate" process is completed but the certificate 




NEW TOPIC: Export Java Certificate 

To export a Java certificate, click on the 

icon or right-click and then select the "Export Java Certificate" 


The "Export Java Certificate" dialog will display. Fill in the 


- Enter or browse an exported certificate file in the "Export 

certificate to file" box. Note that the exported file must be 

valid and in the local Windows machine. The file extension is 

usually .cer, .crt or .cert. 



NEW TOPIC: Delete Java Certificate 

To delete a Java certificate, click on the 

icon or right-click and then select the "Delete" from the pop-up 

menu. 

The "confirm delete" pop-up dialog will display. 

Hit OK button. 

If no error message is displayed, the "Delete Java Certificate" 

process is completed and the certificate is successfully deleted 

from the keystore. If server responds with a message saying "The 

requested command will be saved in the Java audit database", the 

"Delete Java Certificate" process is completed but the certificate 

has not been successfully deleted from the keystore. The operation 

has been saved in the Java audit database. The user can re-run the 


command. 

NEW TOPIC: Change Java Certificate Alias 

To change Java certificate alias, right-click and then select the 

"Rename". The name will be highlighted. Enter a new name for this 

certificate. Note that the name should be unique in the entire 

keystore. 

If no error message is displayed, the "Change Java Certificate 

Alias" process is completed and the certificate alias has been 

successfully changed. If the server responds with a message 

saying that "The requested command will be saved to the Java audit 

database", the "Change Java Certificate Alias" process is completed 

but the certificate alias has not been changed. The operation has 

been saved in the Java audit database. The user can re-run the 


command. 

378 6875 9497–003


NEW TOPIC: View Java Certificate Properties 

To view Java certificate properties, click on the icon 

or right-click and then select the "Properties" from the pop-up 

menu. 

The properties dialog will display and show the properties such as 

common name, issuer, version, serial number and fingerprints. 

Component: INSTALLATION PRI-11493106 


SYMPTOMS: 






Security Administration Guide (8600 0973), Section 9 

Introduction to Security Center, page 9-3. Add the following 

paragraph at the end of Overview of Security Center subsection: 

By default, the Security Center installation installs a 32-bit 









32-bit applications (such as SecurityCenter) use the 32-bit version, 


version. 

SecurityCenter Help (4310 9263) 

Add the same new paragraph to Security Center Help file, Section 

Getting Started, subsection What Is Security Center? after Locum 

SafeSurvey bullet. 

Component: RBACSUPPORT PRI-11533388 





6875 9497–003 379








|-- /1\ -- RBAC ---| 

In the "Explanation" that follows replace the last sentence of the 

second paragraph (replace "Note that the SNA minor type has no 

subtypes") with 








|-- /1\ -- RBAC ---| 


RBAC 




follows. 










the name. 

380 6875 9497–003













5 ADD_ROLE 

6 DELETE_ROLE 


















6875 9497–003 381










Minor 




Component: RBACSUPPORT PRI-11591833 

Log Inquire Permission Failures 

SYMPTOMS: 

If an INQUIRE_PERMISSION call indicates that the task does not have 

the requested permission, this may be an indication of violation of 

role policy. This violation should be logged. 


If the PERMISSIONID parameter passed to INQUIRE_PERMISSION (or 

INQUIRE_PERMISSION_FOR_TASK) is a negative value, a Major Type 6, 

Minor Type 24 (Role Based Access Control) log entry is generated. 

The description of the log entry in the System Log Programming 

Reference manual (form # 8600 1807) is updated as follows: 

Word 4, Value 20, INQUIRE_PERMISSION 

Word 12, Mix number or 0 

For INQUIRE_PERMISSION, a mix number is stored (if the task 

supplied is an active task). 

382 6875 9497–003

Component: SYSTEMPOLICY PRI-11479944 



SYMPTOMS: 

Export and Import of IPsec policies are disabled in the 

IPsec policy menu. 


This feature is now implemented. 












check box. 






















6875 9497–003 383




























shown. 












be discarded. 




384 6875 9497–003














to error. 






Implement testing of IPsec policies within the View & Update 

Wizards. 

SYMPTOMS: 

Testing of IPsec policies cannot be done before deployment to the 

ClearPath MCP environment. 




Implement testing of IPsec policies within the View & Update 

Wizards. 

SYMPTOMS: 

Testing of IPsec policies cannot be done before deployment to the 

ClearPath MCP environment. 



6875 9497–003 385




SYMPTOMS: 

Export and Import of IPsec policies are disabled in the 

IPsec policy menu. 














check box. 






















386 6875 9497–003




























shown. 












be discarded. 




6875 9497–003 387














to error. 






DNOTE for ADD/IPSEC/TESTING/WIZARD (Feature 1935, 1st half). 

SYMPTOMS: 

DNOTE for feature. 



Section 9, Page 9-1/2: 

- Modify the paragraph about "IPsec Policy module" to include 

test (where it mentions "create, modify, reorder, and delete") 

- Modify the last sentence of the paragraph about "IPsec Policy 

module" to "Refer to Section 10 for more details on configuring, 

testing and deploying IPSec policies." 

Section 10, Page 10-9: 

- Add the following new section, "Testing IPsec Policies", BEFORE 

"Committing the Policies to the MCP Environment" section 

"Testing IPsec Policies" 

The IPsec policies should be tested before deployment to insure 

that the network access is not affected (since IPsec's default 

action is to DISCARD any pockets not explicitly matched by a 

policy). 

IPsec Testing is part of the Update and View IPsec Policies 

wizards. 

388 6875 9497–003


Use the following procedure to create an IPsec policy test: 

1. Right-click the IPsec Policy node in the scope pane, and then 

click Update or View IPsec Policies. 

The IPsec Policy Wizard Welcome screen appears. 

2. Click Next. 

The IPsec Policies dialog box now appears. 


The Test IPsec Policies dialog box appears. 

4. Enter the values for sample network traffic to perform a test of 

the IPsec policies list: 

- Unique Test Name 

- Upper Layer Protocol (TCP, UDP, ICMPv6 or BIP) 

- Direction (IN or OUT) 

- Local IP address 

- Remote IP address 

- Local Port or ICMP Type/Code Range 

- Remote Port Range 

NOTE: Only one port type range (either local or remote) is 

supported by the IPsec Test Wizard. 

For example, enter the following test values: 

Test Name = TEST_PROTECTFTP 

ULP = TCP 

Direction = IN 

Local IP Address = FEC0::2222:A00:BFF:FE3A:100 

Local Port or ICMP Type/Code = 500 

Remote IP Address = FEC0::2222:A00:BFF:FE3A:127 

Remote Port = ANY 

5. After specifying the values needed, click Test. 

The IPsec Test Results dialog box appears. 

For example, using the Example Policies 1 through 8 from the 

previous section and the test example from step 4, the IPsec Te 

Wizard will display three test result entries in the table on t 

IPsec Test Results dialog, where 

- The first result is for local port 500, remote ports 1 to 19 

will be set to BYPASS 

- The second result is for local port 500, remote ports 20 to 21 

will be set to PROTECT 

- The last, third result, is for local port 500, remote ports 22 

to 65535 will be set to BYPASS 

If you save the IPsec test results to a file, the following test 

result details are stored for your reference: 

6875 9497–003 389


Test Result for Test = TEST_PROTECTFTP 

ULP = TCP 


Test Result = BYPASS 




Remote Port = 1 - 19 

First Matched Policy = BYPASSALLIN 

Matching Bypass Polices = BYPASSALLIN 

Matching Discard Polices = None 

Matching Protect Polices = None 


ULP = TCP 


Test Result = PROTECT 





First Matched Policy = PROTECTFTPIN 



Matching Protect Polices = PROTECTFTPIN 


ULP = TCP 











These IPSec test results indicate that the FTP traffic is allowed 

to bypass IPSec protection for the remote ports 1 - 19 and 22 - 

65535. While the FTP traffic for the remote ports 20 - 21 matched 

bypass policy, it was protected as defined in the first matching 

PROTECTFTPIN policy. 

NOTE: Because the order of the IPsec policies in the list is 

crucial to setting the desired traffic control, the results of 

the IPsec test shows ALL matching policies as well as the one 

that will be used. 

6. Double-click on specific test result entry to display matching 

IPsec policies lists. 

The Matching Policies dialog box appears. 

390 6875 9497–003


This dialog presents all matching IPSec Policies for one test 

result entry in three separate list (DISCARD, PROTECT and 

BYPASS). The first matching policy is marked as . 

7. Double-click on any policy name to display additional information 

about the specific IPsec policy and test. 

The IPSec Property page appears. 

You can switch between property pages in Update IPsec Policies 

Wizards and go back to add, modify, clone, delete or reorder IPSec 

policies allowing you to test the updated IPsec policies list before 

it is committed to the ClearPath MCP database. 

Since the IPsec tests and tests results are discarded upon the 

completion of the View & Update IPsec Policies Wizards, the IPsec 

test summary can be saved locally on a Windows drive and on the MCP 

server in a text file for later reference. 



Topic "IPsec Policy", first paragraph, second sentence 

Please add "test" to the list of operations that can be done on 

IPsec policies (with a link to the new topic below) 

New Topic: 


The IPsec Policies Test Wizard allows you to test the IPsec 

policies before they are committed to the ClearPath MCP 

database. The IPsec policies can be tested as part of the View & 

Update IPsec Policies Wizards. 

The IPsec policy tests are created to verify the handling of 

both inbound and outbound IP packets. You can specify IPsec 

tests to examine whether the order in the IPsec policy list sets 

the desired traffic control. The attributes of the IPsec test 

are matched against the IPsec policy list and the results of 

this evaluation are collected in the test results summary. 

The IPsec test results indicate whether the traffic packet or 

the range of packets specified in the test are allowed to BYPASS 

protection, will be DISCARDED or PROTECTED as defined in the 

matching policy. The packet disposition is set to first matching 

IPsec policy; otherwise, if no matches are found, the packet 

traffic is discarded by default. 


Wizards and go back to IPsec Policies dialog box to add, modify, 

clone, delete or reorder IPSec policies allowing you to retest 

the updated IPsec policies list. 

6875 9497–003 391



completion of the View & Update IPsec Policies Wizards, the 

IPsec test summary can be saved locally on a Windows drive and 

on the MCP server in a text file. 

Please add new sub topic "Starting an IPsec Policy Test" under the 

"Testing IPsec Policies" topic. 

New Sub-topic: 

"Starting an IPsec Policy Test" 






The IPsec Policies dialog box appears. 



4. Enter the values for sample network traffic to perform a test 

of the IPsec policies list: 








NOTE: Only one port type range is supported by the IPsec Test 

Wizard. 



The test result entries are marked to indicate whether the 

packet is PROTECTED, BYPASSED or DISCARED as defined in the 

matching policies being tested. The dialog table contains the 

cumulative test results for this session. 

6. Click Save to save the IPsec test summary locally on a 

Windows drive or on the MCP server in a text file. 

7. Double-click on specific test result entry to display 

matching IPsec policies lists. 



392 6875 9497–003


crucial to setting the desired traffic control, this dialog 

displays ALL matching IPsec Policies for one test result 

entry in three separate lists (DISCARD, PROTECT and BYPASS) 

as well as the one that will be used. The first matching 

policy is marked as . 

8. Double-click on any policy name to display additional 

information about the specific IPsec policy and test. 


Please add two new help pages titled "IPsec Testing Results" and 

"Matching IPsec Policies" which only be accessible from the Help 

buttons of the IPsec Testing Wizard dialogs and will not be 

represented as the actual topics. 

New Topic: 

"IPsec Testing Results" 

The IPsec Testing Results dialog table contains the cumulative 

test results for the current test session. 







Use the following procedure to get more detail test results 

information: 






Because the order of the IPsec policies in the list is 









New Topic: 

"Matching IPsec Policies" 

6875 9497–003 393


The IPsec policies are stored in the ordered list (the IPsec 

module selects the first policy for which the packet matches the 

traffic). So to help facilitate the right traffic control, the 

Matching IPsec Policies dialog displays ALL matching IPsec 

Policies for one test result entry in three separate lists 

(DISCARD, PROTECT and BYPASS) as well as the one that will be 

used. This first matching policy is marked as . 

You can double-click on any policy name to display additional 

information about the specific IPsec policy and test on the 

IPSec Property page. 


DNOTE for ADD/IPSEC/TESTING/WIZARD (Feature 1935, 1st half). 

SYMPTOMS: 

DNOTE for feature. 



Section 9, Page 9-1/2: 

- Modify the paragraph about "IPsec Policy module" to include 

test (where it mentions "create, modify, reorder, and delete") 

- Modify the last sentence of the paragraph about "IPsec Policy 

module" to "Refer to Section 10 for more details on configuring, 

testing and deploying IPSec policies." 

Section 10, Page 10-9: 

- Add the following new section, "Testing IPsec Policies", BEFORE 

"Committing the Policies to the MCP Environment" section 


The IPsec policies should be tested before deployment to insure 

that the network access is not affected (since IPsec's default 

action is to DISCARD any pockets not explicitly matched by a 

policy). 

IPsec Testing is part of the Update and View IPsec Policies 

wizards. 






394 6875 9497–003

The IPsec Policies dialog box now appears. 




4. Enter the values for sample network traffic to perform a test of 

the IPsec policies list: 








NOTE: Only one port type range (either local or remote) is 

supported by the IPsec Test Wizard. 

For example, enter the following test values: 

Test Name = TEST_PROTECTFTP 

ULP = TCP 





Remote Port = ANY 



For example, using the Example Policies 1 through 8 from the 

previous section and the test example from step 4, the IPsec Te 

Wizard will display three test result entries in the table on t 

IPsec Test Results dialog, where 

- The first result is for local port 500, remote ports 1 to 19 

will be set to BYPASS 

- The second result is for local port 500, remote ports 20 to 21 

will be set to PROTECT 

- The last, third result, is for local port 500, remote ports 22 

to 65535 will be set to BYPASS 

If you save the IPsec test results to a file, the following test 

result details are stored for your reference: 


ULP = TCP 







6875 9497–003 395







ULP = TCP 


Test Result = PROTECT 





First Matched Policy = PROTECTFTPIN 



Matching Protect Polices = PROTECTFTPIN 


ULP = TCP 











These IPSec test results indicate that the FTP traffic is allowed 

to bypass IPSec protection for the remote ports 1 - 19 and 22 - 

65535. While the FTP traffic for the remote ports 20 - 21 matched 

bypass policy, it was protected as defined in the first matching 

PROTECTFTPIN policy. 


crucial to setting the desired traffic control, the results of 

the IPsec test shows ALL matching policies as well as the one 

that will be used. 

6. Double-click on specific test result entry to display matching 

IPsec policies lists. 


This dialog presents all matching IPSec Policies for one test 

result entry in three separate list (DISCARD, PROTECT and 

BYPASS). The first matching policy is marked as . 

7. Double-click on any policy name to display additional information 

about the specific IPsec policy and test. 


396 6875 9497–003



Wizards and go back to add, modify, clone, delete or reorder IPSec 

policies allowing you to test the updated IPsec policies list before 

it is committed to the ClearPath MCP database. 


completion of the View & Update IPsec Policies Wizards, the IPsec 

test summary can be saved locally on a Windows drive and on the MCP 

server in a text file for later reference. 



Topic "IPsec Policy", first paragraph, second sentence 

Please add "test" to the list of operations that can be done on 

IPsec policies (with a link to the new topic below) 

New Topic: 


The IPsec Policies Test Wizard allows you to test the IPsec 

policies before they are committed to the ClearPath MCP 

database. The IPsec policies can be tested as part of the View & 

Update IPsec Policies Wizards. 

The IPsec policy tests are created to verify the handling of 

both inbound and outbound IP packets. You can specify IPsec 

tests to examine whether the order in the IPsec policy list sets 

the desired traffic control. The attributes of the IPsec test 

are matched against the IPsec policy list and the results of 

this evaluation are collected in the test results summary. 








Wizards and go back to IPsec Policies dialog box to add, modify, 

clone, delete or reorder IPSec policies allowing you to retest 

the updated IPsec policies list. 


completion of the View & Update IPsec Policies Wizards, the 

IPsec test summary can be saved locally on a Windows drive and 

on the MCP server in a text file. 

Please add new sub topic "Starting an IPsec Policy Test" under the 

"Testing IPsec Policies" topic. 

New Sub-topic: 

6875 9497–003 397


"Starting an IPsec Policy Test" 






The IPsec Policies dialog box appears. 



4. Enter the values for sample network traffic to perform a test 

of the IPsec policies list: 








NOTE: Only one port type range is supported by the IPsec Test 

Wizard. 



The test result entries are marked to indicate whether the 

packet is PROTECTED, BYPASSED or DISCARED as defined in the 

matching policies being tested. The dialog table contains the 

cumulative test results for this session. 














398 6875 9497–003



Please add two new help pages titled "IPsec Testing Results" and 

"Matching IPsec Policies" which only be accessible from the Help 

buttons of the IPsec Testing Wizard dialogs and will not be 

represented as the actual topics. 

New Topic: 

"IPsec Testing Results" 

The IPsec Testing Results dialog table contains the cumulative 

test results for the current test session. 







Use the following procedure to get more detail test results 

information: 






Because the order of the IPsec policies in the list is 









New Topic: 

"Matching IPsec Policies" 

The IPsec policies are stored in the ordered list (the IPsec 

module selects the first policy for which the packet matches the 

traffic). So to help facilitate the right traffic control, the 

Matching IPsec Policies dialog displays ALL matching IPsec 

Policies for one test result entry in three separate lists 

(DISCARD, PROTECT and BYPASS) as well as the one that will be 

used. This first matching policy is marked as . 

You can double-click on any policy name to display additional 

6875 9497–003 399


information about the specific IPsec policy and test on the 

IPSec Property page. 

Component: USERCENTER PRI-11506879 


SYMPTOMS: 












migration. 










Attribute) 






entry. 



words 


400 6875 9497–003

SLICE 














Component: ALL PRI-11534813 

$OPTIMIZE Has No Affect On $BOUNDS 

SYMPTOMS: 

The OPTIMIZE option has no affect on the BOUNDS option. Users should 

be aware that the bounds checking code is not removed when the 

OPTIMIZE option is used. 


The OPTIMIZE option has no affect on the BOUNDS option, therefore 

users may want to consider adding $RESET BOUNDS when the OPTIMIZE 

option is used. 

The COBOL ANSI-85 Programming Reference Manual, Volume 1: Basic 

Implementation (8600 1518-309) should be updated as follows: 

In Section 15. Compiler Operations; Compiler Options; OPTIMIZE 

Option in the description, add the above sentence to the end of the 

first paragraph. 

The C Programming Reference Manual, Volume 1: Basic Implementation 

(8600 2268-204) should be updated as follows: 

In Section 10. Compiler Control Options; Syntax for Compiler 

Control Options (CCRs); OPTIMIZE Option in the description, add the 

above sentence to the end of the first paragraph. 

The Pascal ANSI-83 Programming Reference Manual (8600 1732-001) 

should be updated as follows: 

In Section 17. Compiling Your Program; Using Compiler Control 

6875 9497–003 401


Records; Syntax for Compiler Control Options; OPTIMIZE Option, add 

the above sentence to the end of the first paragraph. 


COBOL85 Epilog Procedure In Host Program Is Allowed 

SYMPTOMS: 

The COBOL85 manual states: 

A program with an EPILOG PROCEDURE declaration cannot be used as 

the host code file when running BINDER. 

However, the COBOL85 compiler allows an EPILOG PROCEDURE declaration 

in a host program used as the host file for the BINDER. 


The manual is incorrect. This restriction should be removed from the 

documentation. 

In the COBOL ANSI-85 Programming Reference Manual, Volume 1: Basic 

Implementation (8600 1518-308); Section 8. Procedure Division 

Statements S-Z; USE Statement; Format 4. USE AS EPILOG PROCEDURE 

under the Explanation text in the Restrictions on Epilog Procedures 

remove the following sentence: 

A program with an EPILOG PROCEDURE declaration cannot be used as 

the host code file when running BINDER. 


New STERNWARN CCI For Deimplementation Warning 

SYMPTOMS: 

The COBOL85 compiler needs to distinguish some of the 

warning messages from the rest. For example, the file 

attribute deimplementation warning messages should 

appear on the screen under Cande compile while allowing 

the compile to complete. This helps to grab the 

programmer's attention to discourage the future use 

of the construct. 




Section 15. Compiler Operations 

Compiler Options 

Add the following for a new option STERNWARN. 

402 6875 9497–003

STERNWARN Option 

Type: Boolean 

Default: TRUE 


This option controls whether the compiler issues certain 

warning messages to the CANDE terminal during compilation. 

The following table describes the effects of this option. 

Option Setting Value Description 

-------------- ----- ----------- 

RESET FALSE The compiler lists no warning messages 

to the CANDE terminal. 

SET TRUE The compiler lists certain warning messages 


The STERNWARN option is not affected by the WARNSUPR 

option. 


New STERNWARN CCI For Deimplementation Warning 

SYMPTOMS: 

The COBOL85 compiler needs to distinguish some of the 

warning messages from the rest. For example, the file 

attribute deimplementation warning messages should 

appear on the screen under Cande compile while allowing 

the compile to complete. This helps to grab the 

programmer's attention to discourage the future use 

of the construct. 




Section 15. Compiler Operations 

Compiler Options 

Add the following for a new option STERNWARN. 

STERNWARN Option 

Type: Boolean 

Default: TRUE 

This option controls whether the compiler issues certain 

warning messages to the CANDE terminal during compilation. 

The following table describes the effects of this option. 

6875 9497–003 403


Option Setting Value Description 

-------------- ----- ----------- 

RESET FALSE The compiler lists no warning messages 


SET TRUE The compiler lists certain warning messages 


The STERNWARN option is not affected by the WARNSUPR 

option. 



SYMPTOMS: 






8600 1526-204, 







{---- } [ -- ---- ] 

{MODIFY } 

{----- } 







404 6875 9497–003




SYMPTOMS: 






8600 1526-204, 







{---- } [ -- ---- ] 

{MODIFY } 

{----- } 









SYMPTOMS: 






8600 1526-204, 




6875 9497–003 405





------ [ -- ---- ] 









SYMPTOMS: 






8600 1526-204, 







------ [ -- ---- ] 







406 6875 9497–003

SORT 

Component: SORT PRI-11351387 


Generate Syntax Errors For Invalid Numeric Sort Key Lengths 

SYMPTOMS: 

Sort program faults at run-time when key length is large and type is 

ALPHA NUMERIC, ALPHA NUMERIC SIGN or PACKED SIGN. 

SORT Program- 

MEMORYONLY 

FILE IN(TITLE="SORT/INPUT") 

FILE OUT(TITLE="SORT/OUTPUT") 

KEY(1 24 ALPHA NUMERIC) 

KEY(1 24 ALPHA NUMERIC SIGN TRAILING ZONE) 

KEY(1 25 ALPHA NUMERIC SIGN TRAILING SEPARATE) 

KEY(1 25 PACKED SIGN TRAILING) 

KEY(1 24 ALPHA NUMERIC SIGN LEADING ZONE) 

KEY(1 25 ALPHA NUMERIC SIGN LEADING SEPARATE) 

KEY(1 25 PACKED SIGN LEADING) 

This program faults at run-time- 

R 

#RUNNING 2615 

#2615 INVALID OPERATOR @ 00A:0001:2 

#F-DS @ 00A:0001:2, 002:0214:1. 

#ET=0.1 PT=0.0 IO=0.1 


Please make the following changes to the Unisys MCP/AS SORT Language 

Programming Reference Manual (8807 6583-002) Section 2. Sort Program 

Structure, Basic Syntax Component, under the heading Type: 

On page 2-9, add the following two sentences to the description of 

LENGTH that appears immediately after Table 2-1 (Key and Data Field 

Storage). 

For UNSIGNED or SIGNED ZONE numeric value comparisons, the maximum 

value of the parameter in the is 23. 

For SIGNED SEPARATE numeric value comparisons, the maximum value of 

the parameter in the is 24. 

6875 9497–003 407


Component: SORT PRI-11538754 

Generate Syntax Errors For Invalid Numeric Sort Key Lengths 

SYMPTOMS: 

Sort program faults at run-time when key length is large and type 

is ALPHA NUMERIC, ALPHA NUMERIC SIGN or PACKED SIGN. 

SORT Program- 

MEMORYONLY 

FILE IN(TITLE="SORT/INPUT") 

FILE OUT(TITLE="SORT/OUTPUT") 

KEY(1 24 ALPHA NUMERIC) 

KEY(1 24 ALPHA NUMERIC SIGN TRAILING ZONE) 

KEY(1 25 ALPHA NUMERIC SIGN TRAILING SEPARATE) 

KEY(1 25 PACKED SIGN TRAILING) 

KEY(1 24 ALPHA NUMERIC SIGN LEADING ZONE) 

KEY(1 25 ALPHA NUMERIC SIGN LEADING SEPARATE) 

KEY(1 25 PACKED SIGN LEADING) 

This program faults at run-time- 

R 

#RUNNING 2615 

#2615 INVALID OPERATOR @ 00A:0001:2 

#F-DS @ 00A:0001:2, 002:0214:1. 

#ET=0.1 PT=0.0 IO=0.1 


Please make the following changes to the Unisys MCP/AS SORT Language 

Programming Reference Manual (8807 6583-002) Section 2. Sort Program 

Structure, Basic Syntax Component, under the heading Type: 

On page 2-9, add the following two sentences to the description of 

LENGTH that appears immediately after Table 2-1 (Key and Data Field 

Storage). 

For UNSIGNED or SIGNED ZONE numeric value comparisons, the maximum 

value of the parameter in the is 23. 

For SIGNED SEPARATE numeric value comparisons, the maximum value of 

the parameter in the is 24. 

408 6875 9497–003

TADS 

Component: TADS PRI-11438211 


BYE In Multitasking Environment Could Cause DS of Subordinate 

Task 

SYMPTOMS: 

While running TADS in a multitasking environment, if the user program 

is stopped while in a subordinate task, then entering BYE or END may 

cause that subordinate task to terminate with a DS fault rather than 

terminating normally. 


In the ALGOL Test and Debug System (TADS) Programming Guide 

(8600 2144-002); Section 4. Complex Testing Environments; 

Multitasking add the following paragraph: 

While running TADS in a multitasking environment, if the user 

program is stopped while in a subordinate task, then entering BYE 

or END may cause that subordinate task to terminate with a DS fault 

rather than terminating normally. 

TELNET 

Component: TELNETSUPPORT PRI-11567967 

Support Telnet Sessions Connected over SSL 


Telnet now supports client connections over SSL. The following 

new configuration options control these connections. 

PORT_NUMBER_SSL (default 992) 

The PORT_NUMBER_SSL option defines the TCP port number used for 

secure connections. 

SSL_KEY_CONTAINER (default TELNET_SSLKEY) 

The SSL_KEY_CONTAINER option defines the key container where 

the host certificate is stored. This certificate is transmitted 

to the client for authentication purposes. 

SECURITY SECURECOMM (default ALLOWED) 

The SECURECOMM security option determines whether secure, 

non-secure or both connections are offered. The values 

6875 9497–003 409


REQUIRED, DISABLED, and ALLOWED correspond to these three 

choices. The value of the Telnet SECURECOMM option is read- 

only. To change it, use the SECOPT (Security Options) system 

command. 

Note that if the value of the SECURECOMM security option is 

ALLOWED, the number of passive offers that Telnet makes will be 

double the option value (Telnet will maintain the same number of 

secure and non-secure passive offers.) 

Component: TELNETSUPPORT PRI-11576605 

Support Telnet Sessions Connected over SSL 


Telnet now supports client connections over SSL. The following 

new configuration options control these connections. 

PORT_NUMBER_SSL (default 992) 

The PORT_NUMBER_SSL option defines the TCP port number used for 

secure connections. 

SSL_KEY_CONTAINER (default TELNET_SSLKEY) 

The SSL_KEY_CONTAINER option defines the key container where 

the host certificate is stored. This certificate is transmitted 

to the client for authentication purposes. 

SECURITY SECURECOMM (default ALLOWED) 

The SECURECOMM security option determines whether secure, 

non-secure or both connections are offered. The values 

REQUIRED, DISABLED, and ALLOWED correspond to these three 

choices. The value of the Telnet SECURECOMM option is read- 

only. To change it, use the SECOPT (Security Options) system 

command. 

Note that if the value of the SECURECOMM security option is 

ALLOWED, the number of passive offers that Telnet makes will be 

double the option value (Telnet will maintain the same number of 

secure and non-secure passive offers.) 

410 6875 9497–003

WFL 

Component: WFL PRI-11417132 

Emit Warning If Predefined Word is Used 


SYMPTOMS: 

WFL should emit a warning if a predefined word is used. 

For example: 

BEGIN JOB; 

INTEGER COPY; 

COPY := 1; 

COPY X AS Y; 

END JOB. 


When a predefined word is used, the WFL compiler now gives the 

warning: 

USE OF PREDEFINED WORD COULD CAUSE UNEXPECTED RESULTS 

The Work Flow Language (WFL) Programming Reference Manual 

(8600 1047-508) needs to be modified as follows: 


Reserved Words remove BINARY from the list of reserved words. 


Predefined Words add the following words to the list of predefined 

words in their proper alphabetical location: 

ALTER, ARCHIVE, CREATE, MKDIR, MOVE, REPLACE, RESTOREADD, 

RESTOREREPLACE, UNWRAP, VOLUME, WRAP. 


WARNSUPPRESS Option Now Available 

SYMPTOMS: 

Customer would like to be able to suppress warning messages. 


The WARNSUPPRESS option is now available in WFLSUPPORT. 

WARNSUPPRESS Option 

 

--- $ ------------------ WARNSUPPRESS --| 

|- $$ -| |- RESET -| 

|- SET ---| 

6875 9497–003 411


Explanation 

This control option controls the emitting of warning messages by 

the WFL compiler. SET is an optional action indicator that prevents 

warning messages from being emitted by the WFL compiler. RESET is 

an optional action indicator that causes warning messages to be 

emitted by the WFL compiler. SET is the default value. If the job 

was started through CANDE, the default value is RESET. 

Example 

In this example, the WARNSUPPRESS option is used to prevent a 

warning message from being emitted by the WFL compiler: 

$SET WARNSUPPRESS 

BEGIN JOB NOWARN; 

FAMILY ABCDEFGHIJKLMNOPQRSTUVWXYZ = DISK ONLY; 

COPY X AS Y; 

END JOB 

If the above job had $RESET WARNSUPPRESS on the first line, then 

the following warning message would be emitted: 

WARNING: FAMILY NAME LONGER THAN 17 CHARACTERS HAS BEEN TRUNCATED 


Give MCP Deimplementation Messages While Parsing Task 

Attributes 

SYMPTOMS: 

In CANDE, when a deimplemented task attribute is used in a 

PRINTDEFAULTS value, the deimplementation warning is not given. 

For example: 

RUN $SYSTEM/DUMPALL("LIST X");PRINTDEFAULTS=(SAVEBACKUPFILE) 


A new field was added to the HANDLEATTRIBUTES result. 

[03:01] AIATTDEIMPF 

If 1 then an MCP deimplementation warning or error exists. 

In this case, AIERRNUMF is the MCP deimplementation number. 

In the Task Attributes Programming Reference Manual (8600 0502-409); 

Section 1. Accessing Task Attributes; Programmer Access to Task 

Attributes; Assigning Task Attributes Through HANDLEATTRIBUTES; 

Procedure Result; modify or add to the fields as follows: 

Add the following text to the explanation of [23:16]: 

If AIATTDEIMPF is 1, then this field is the MCP 

deimplementation number. 

Replace the explanation of [07:05] with the following: 

[07:04] This field is always 0. 

Add the following field before [02:01]: 

[03:01] AIATTDEIMPF 

If 1 then an MCP deimplementation warning or error 

exists. In this case, AIERRNUMF is the MCP 

deimplementation number. 

412 6875 9497–003



CHANGE and REMOVE Statements Return Result Information 

SYMPTOMS: 

WFL provides no method of determining whether a CHANGE or REMOVE 

was successful. 


The syntax of the CHANGE and REMOVE statements has been extended to 

allow the user to determine whether the action was successful and 

the nature of any failure. 

The CHANGE statement now allows up to 6 results to be returned and 

the REMOVE statement allows up to 5 results. The CHANGE statement 

can now be followed by an optional results structure -- [b1, i, b2, 

b3, b4, b5]. The REMOVE statement can now be followed by an 

optional results structure -- [b1, i, b2, b3, b4]. Parameters are 

optional, so for example [b1, i] is syntactically correct. 

However, if a parameter is specified, all preceding parameters must 

also be specified. The parameters return the following 

information: 

Variable Type Description 

b1 Boolean TRUE if a failure occurred. FALSE is all 

files and directories were changed or removed 

i Integer Total number of changed or removed files 

b2 Boolean TRUE if at least one file or directory was 

not removed or changed because it was not 

present 

b3 Boolean TRUE if at least one file was not removed or 

changed because the file was a locked file 

b4 Boolean TRUE if at least one file was not removed 

because of a security error 

b5 Boolean [CHANGE only] TRUE if at least one file was 

not changed because the destination file 

already existed 

A job that uses this new syntax will be aborted if it is run on a 

12.0 or earlier MCP. 

Example: 

BEGIN JOB DEMONSTRATE/CHANGE/AND/REMOVE; 

BOOLEAN BFAILED, BMISSING, BLOCKED, BSEC, BDUP; 

INTEGER COUNT; 

CHANGE CHANGETEST1/= TO CHANGETEST3/=, 

CHANGETEST5/= TO CHANGETEST2/=, 

CHANGETEST6 TO CHANGETEST7 

[BFAILED, COUNT, BMISSING, BLOCKED, BSEC, BDUP]; 

6875 9497–003 413


DISPLAY "Change test: " & STRING (COUNT, *) & " files changed"; 


DISPLAY "All files changed"; 





IF BSEC THEN 


IF BDUP THEN 

DISPLAY "Duplicate files seen"; 



CHANGETEST7 

[BFAILED, COUNT, BMISSING, BLOCKED, BSEC]; 








IF BSEC THEN 




CHANGETEST7 

[BFAILED, COUNT]; % Not all variables are needed 




END JOB 


Extend Maximum String Length to 1800 Characters 

SYMPTOMS: 

The maximum string length is inconsistent. 

In some cases the maximum length is 1024 and others it is 1032. The 

maximum string length should be the same in all cases. 


The maximum length of a string variable or string constant or string 

parameter is now 1800 characters. 

Functions that work with strings now handle 1800 characters. 

414 6875 9497–003


Add TIMEDATE(HHMMSSPPPP) 


SYMPTOMS: 

The TIMEDATE function should show greater granularity than is offered 

by TIMEDATE(HHMMSS). 


The TIMEDATE function is enhanced to allow TIMEDATE(HHMMSSPPPP) 

which returns the time as a string of ten characters. This function 

is similar to TIMEDATE(HHMMSS) except that the last four characters 

represent the ten thousandths of a second. 

In the Work Flow Language (WFL) Programming Reference Manual 

(8600 1047-509); page 7-23 under the TIMEDATE Function: 

In the railroad diagram for after the first 

line add the line: 

|-- HHMMSSPPPP -------| 

After the description of TIMEDATE (HHMMSS) add the following 

description: 

TIMEDATE (HHMMSSPPPP) 

Returns the time as a string of ten characters. The first two 

characters represent the hours on a 24-hour clock, the next two 

characters represent the minutes, the next two characters 

represent the seconds, and the last four characters represent the 

ten thousandths of a second. For example: 

"1709007124" 


Allow Nested INCLUDE Files 

SYMPTOMS: 

WFL does not allow an INCLUDE file to contain a $INCLUDE option. 


WFL now allows an INCLUDE control option to appear in a file that 

is being included. Up to 5 levels of nesting are supported. 

Change the Work Flow Language (WFL) Programming Reference Manual 

(form # 8600 1047) as follows: 

In the "INCLUDE Option" topic of the "WFL Control Options" section, 

replace the paragraph "INCLUDE options cannot be nested ..." with 

6875 9497–003 415


The included records can themselves contain INCLUDE options; in 

this way, included source input can be nested up to five levels 

deep. 


Add TIMEDATE(YYYYMMDDHHMMSSPPPP) 

SYMPTOMS: 

The TIMEDATE function should show greater granularity than is offered 

by TIMEDATE(YYYYMMDDHHMMSS). 


The TIMEDATE function is enhanced to allow 

TIMEDATE(YYYYMMDDHHMMSSPPPP) which returns the time and date as a 

string of 18 characters. This function is similar to 

TIMEDATE(YYYYMMDDHHMMSS) except that the last four characters 

represent the ten thousandths of a second. 


(8600 1047-509); page 7-23 under the TIMEDATE Function: 

In the railroad diagram for after the second 

current line (that allows YYYYMMDDHHMMSS) add the line: 

|-- YYYYMMDDHHMMSSPPPP --| 

After the description of TIMEDATE (YYYYMMDDHHMMSS) add the 

following description: 

TIMEDATE (YYYYMMDDHHMMSSPPPP) 

Returns the time and date as a string of 18 characters. The 

first eight characters represent the date: four characters for 

the year, two characters for the month, and two characters for 

the day of the month. The last ten characters represent the 

time: two characters for the hours on a 24-hour clock, two 

characters for the minutes, two characters for the seconds, and 

four characters for the ten thousandths of a second. For example: 

"200806131122198516" 


WARNSUPPRESS Option Now Available 

SYMPTOMS: 

Customer would like to be able to suppress warning messages. 


The WARNSUPPRESS option is now available in WFLSUPPORT. 

416 6875 9497–003

WARNSUPPRESS Option 

 

--- $ ------------------ WARNSUPPRESS --| 

|- $$ -| |- RESET -| 

|- SET ---| 


Explanation 

This control option controls the emitting of warning messages by 

the WFL compiler. SET is an optional action indicator that prevents 

warning messages from being emitted by the WFL compiler. RESET is 

an optional action indicator that causes warning messages to be 

emitted by the WFL compiler. SET is the default value. If the job 

was started through CANDE, the default value is RESET. 

Example 

In this example, the WARNSUPPRESS option is used to prevent a 

warning message from being emitted by the WFL compiler: 

$SET WARNSUPPRESS 

BEGIN JOB NOWARN; 

FAMILY ABCDEFGHIJKLMNOPQRSTUVWXYZ = DISK ONLY; 

COPY X AS Y; 

END JOB 

If the above job had $RESET WARNSUPPRESS on the first line, then 

the following warning message would be emitted: 

WARNING: FAMILY NAME LONGER THAN 17 CHARACTERS HAS BEEN TRUNCATED 


Catch Invalid Hostname Error 

SYMPTOMS: 

WFL allows a hostname to be specified with an underscore ("_") or a 

hyphen ("-") in it. An underscore or hyphen is not allowed by the 

system and should not be allowed by WFL. 


A valid hostname contains from 1 to 17 alphanumeric characters that 

include the uppercase letters A through Z and the numerals 0 through 

9 only. 

WFL now disallows a hostname if it contains an underscore or hyphen, 

unless the hostname is within an copy statement that specified FTP 

file transfer service or no file transfer service was specified. 

If no file transfer service was specified and the hostname contains 

an underscore or hyphen then a warning is given. 


(8600 1047-509) please make the following changes: 

6875 9497–003 417


Replace with on page 8-6. 

Replace with on pages 

2-6 (twice), 2-7, 3-2, 3-3 (three times), 3-6, 3-9, and 8-7. 

Move the railroad diagram for from page 6-185 to 

page 8-6 or 8-7 in Section 8. Basic Constructs. 



Remove the railroad diagram for from page 6-120. 

On page 6-76 add the following sentence to the description of 

: 

A volume name cannot contain a period for a file kind of DISK. 


START AND WAIT Still Waits When Used in PROCESS Statement 

SYMPTOMS: 

A dependent job initiated through a START AND WAIT statement must 

complete before the next WFL statement can be processed. This 

applies even if the START AND WAIT statement is used in a PROCESS 

statement. 

Since it makes no sense to use START AND WAIT in a PROCESS statement, 

this syntax should be disallowed. Note that is not listed as part of the syntax. 


If a START AND WAIT statement is found as part of a PROCESS 

statement, the syntax error: 

CANNOT USE START AND WAIT IN A PROCESS STATEMENT 

is generated. 

Add the following additional note to the notes listed for the 

START AND WAIT Statement in the Statements section of the Work 

Flow Language (WFL) Programming Reference Manual (form # 

8600 1047): 

o The START AND WAIT statement cannot be used in a PROCESS 

statement 

418 6875 9497–003


Catch Invalid Hostname Error 


SYMPTOMS: 

WFL allows a hostname to be specified with an underscore ("_") or a 

hyphen ("-") in it. An underscore or hyphen is not allowed by the 

system and should not be allowed by WFL. 


A valid hostname contains from 1 to 17 alphanumeric characters that 

include the uppercase letters A through Z and the numerals 0 through 

9 only. 

WFL now disallows a hostname if it contains an underscore or hyphen, 

unless the hostname is within an copy statement that specified FTP 

file transfer service or no file transfer service was specified. 

If no file transfer service was specified and the hostname contains 

an underscore or hyphen then a warning is given. 


(8600 1047-509) please make the following changes: 

Replace with on page 8-6. 

Replace with on pages 

2-6 (twice), 2-7, 3-2, 3-3 (three times), 3-6, 3-9, and 8-7. 





Remove the railroad diagram for from page 6-120. 

On page 6-76 add the following sentence to the description of 

: 

A volume name cannot contain a period for a file kind of DISK. 



SYMPTOMS: 





6875 9497–003 419





year. 





 

--+------------------+--+--------------------------------+--| 

| | | | 

+-- + ----+ +-- TODAY -----------------------+ 

| | 

+-- TOMORROW --------------------+ 

| | 

+-- ON --+-----------------+ 

| | 

+-- + ----+ 

 

--+-- -- / -- -- / --+-- ----+--------------+-----| 

| | | | 

| +-- --+ | 

| | 

+-- TODAY -----------------------------------------------+ 

| | 

+-- TOMORROW --------------------------------------------+ 

| | 

+-- ----+-----------------------------+----+ 

| | 

+--- ---+ 

 

--+-- SUNDAY -----+---| 

| | 

+-- MONDAY -----+ 

| | 

+-- TUESDAY ----+ 

| | 


| | 


| | 

+-- FRIDAY -----+ 

| | 


 

+


| | 

---+-----+-----+-+--/1*\-- --+-+-----------------> 

| | | | 

+--,--+ +--/1*\-- ---------+ 

>---+-----+----+-- ----+---------------------------------| 

| | | | 

+--,--+ +-- --+ 


, , and . 

 

--+-- JANUARY ----+---| 

| | 


| | 

+-- MARCH ------+ 

| | 

+-- APRIL ------+ 

| | 

+-- MAY --------+ 

| | 

+-- JUNE -------+ 

| | 

+-- JULY -------+ 

| | 

+-- AUGUST -----+ 

| | 


| | 

+-- OCTOBER ----+ 

| | 


| | 
















Saturday. 


6875 9497–003 421



. 

. 

. 

?END JOB. 


2008. 



. 

. 

. 

?END JOB. 



SYMPTOMS: 








year. 





 

--+------------------+--+--------------------------------+--| 

| | | | 

+-- + ----+ +-- TODAY -----------------------+ 

| | 

+-- TOMORROW --------------------+ 

| | 

+-- ON --+-----------------+ 

| | 

+-- + ----+ 

 

--+-- -- / -- -- / --+-- ----+--------------+-----| 

| | | | 

422 6875 9497–003


| +-- --+ | 

| | 

+-- TODAY -----------------------------------------------+ 

| | 

+-- TOMORROW --------------------------------------------+ 

| | 

+-- ----+-----------------------------+----+ 

| | 

+--- ---+ 

 

--+-- SUNDAY -----+---| 

| | 

+-- MONDAY -----+ 

| | 

+-- TUESDAY ----+ 

| | 


| | 


| | 

+-- FRIDAY -----+ 

| | 


 

+ 

| | | | 

+--,--+ +--/1*\-- ---------+ 

>---+-----+----+-- ----+---------------------------------| 

| | | | 

+--,--+ +-- --+ 


, , and . 

 

--+-- JANUARY ----+---| 

| | 


| | 

+-- MARCH ------+ 

| | 

+-- APRIL ------+ 

| | 

+-- MAY --------+ 

| | 

+-- JUNE -------+ 

| | 

6875 9497–003 423


+-- JULY -------+ 

| | 

+-- AUGUST -----+ 

| | 


| | 

+-- OCTOBER ----+ 

| | 


| | 
















Saturday. 



. 

. 

. 

?END JOB. 


2008. 



. 

. 

. 

?END JOB. 


Assigned to YOURNAME Is Documented Incorrectly 

SYMPTOMS: 

The file attribute YOURNAME is documented incorrectly. 

The WFL manual specifies YOURNAME= and defines 

as . 

424 6875 9497–003


However, only an integer literal (or a string variable containing an 

integer literal) is allowed for a in an FTP copy. 



(8600 1047-509), please update the documentation as follows: 

In Section 6. Statements; COPY or ADD Statement; COPY Request replace 

the railroad diagram for with the following railroad 

diagram and the additional text below it: 

 

----- -----------------------| 

| | 

--- # -- --- 

WINMQ 

The # syntax can be used to dynamically specify a 

port number. The must evaluate to an integer. 


Implement Use of the WinRPC Client Fast Interface 

SYMPTOMS: 

In previous releases, the WinRPC client fast interface is a keyed 

feature. This feature will be available without a key starting 

with release 54.1. There is a performance advantage to using the 

WinRPC client fast interface. 


Make the following change to the ClearPath MCP Interface to Microsoft 

Message Queuing (WinMQ) (6898 5985): 

Add the following to the table in Section 9. Troubleshooting/ 

Understanding HRESULT Status Codes/WinMQ API Support Library 

HRESULT Status Code: 

0xC1FF1038 Indicates that the connection to WinRPC failed. 


Update "Selecting the RPC Server" Section Within the 

Documentation 

SYMPTOMS: 

Documentation not clear on how to select the WinMQ API RPC server. 


Make the following change to the ClearPath MCP Interface to Microsoft 

6875 9497–003 425



Change Section 5. Using the WinMQ Application Program 

Interface (API)/Selecting the RPC Server to be: 

Selecting the WinMQ API RPC Server 

You must use one of the following methods to identify the WinMQ 

API RPC server that provides the MSMQ implementation: 

. Specify a default WinMQ API RPC server during the 

distributed systems services (DSS) registration using the 

TASKSTRING task attribute or by using the 

NA WINMQAPI DEFAULTSERVER command. 

. Use the application TASKSTRING task attribute to specify 

the WinMQ API RPC server. 

. Specify the server name when establishing the connection 

by calling the MQConnectSvr procedure or the MQConnectSvrSec 

procedure. 

Specifying the Default WinMQ API RPC Server 

Using the Library TASKSTRING Task Attribute 

The TASKSTRING task attribute enables you to specify the WinMQ 

API RPC server and can contain a string consisting of 

DEFAULTSERVER=. The default RPC 

server can be set for the WinMQ API support library as 

part of the distributed systems services (DSS) registration. 

Refer to Section 2 of this guide for details. 

Enter the following command to change the default WinMQ API RPC 

server using the library TASKSTRING task attribute: 

NA REG MODIFY PROVIDER WINMQAPISUPPORT 

TASK ATTRIBUTES=(TASKSTRING="DEFAULTSERVER= 

") 

If the support library is currently active, the change does not 

take effect immediately. The newly specified default server 

becomes active the next time the library is initiated. 

Using the NA WINMQAPI DEFAULTSERVER Command 

Enter the following command to set the default server while 

the library is active. The new setting only affects new 

connections to the WinMQ API support library. This command 

changes the DSS registration so that the specified server 

is the default server the next time the library is initiated. 

NA WINMQAPI DEFAULTSERVER 

Specifying the WinMQ API RPC Server Using a User Program 

426 6875 9497–003


There are two ways to specify the WinMQ API RPC server in 

a user program: 

.Using the TASKSTRING task attribute 

.Coding to call the MQConnectSvr procedure or the 

MQConnectSvrSec procedure 

Using the TASKSTRING Task Attribute 

The server linkage is established when the user program calls 

the MQConnect, MQConnectSec, MQConnectSvr, or MQConnectSvrSec 

procedure. The user program TASKSTRING task attribute is 

examined if the server name has not already been provided by 

the MQConnectSvr or MQConnectSvrSec procedure. If the 

TASKSTRING task attribute contains the equation 

"WINMQSERVERNAME=", the specified 

host name or IP address is used. 

Example 

RUN MY/MQAPP; TASKSTRING = "WINMQSERVERNAME=MV-TESTSYS" 

If the host name or IP address is not specified by one of 

these methods, the MQConnect, MQConnectSec, MQConnectSvr, or 

MQConnectSvrSec call fails with an HRESULT of 0xC1FF2056. 


Fix WinMQ API Support Library RPC Reason Codes Within 

Documentation 

SYMPTOMS: 

The reason code 0xC1FF2056 is not specified in the documentation 

within Section 9. Troubleshooting/Understanding HRESULT Status Codes/ 

WinMQ API Support Library RPC Reason Codes. 


Make the following change to the ClearPath MPC Interface to Microsoft 


Change the code column in the table in Section 9. Troubleshooting/ 

Understanding HRESULT Status Codes/WinMQ API Support Library RPC 

Reason Codes as follows: 

Code currently in table Change to 

--------------------------------------------------------- 

0xC1FF2010 0xC1FF200A 

0xC1FF2011 0xC1FF200B 

6875 9497–003 427


0xC1FF2012 0xC1FF200C 

0xC1FF2013 0xC1FF200D 

0xC1FF2014 0xC1FF200E 

0xC1FF2015 0xC1FF200F 

0xC1FF2016 0xC1FF2010 

0xC1FF2017 0xC1FF2011 

0xC1FF2018 0xC1FF2012 

0xC1FF2019 0xC1FF2013 

0xC1FF2020 0xC1FF2014 

0xC1FF2021 0xC1FF2015 

0xC1FF2022 0xC1FF2016 

0xC1FF2023 0xC1FF2017 

0xC1FF2024 0xC1FF2018 

0xC1FF2025 0xC1FF2019 




0xC1FF2032 0xC1FF2020 

0xC1FF2033 0xC1FF2021 

0xC1FF2034 0xC1FF2022 

0xC1FF2035 0xC1FF2023 

0xC1FF2036 0xC1FF2024 

0xC1FF2037 0xC1FF2025 

0xC1FF2038 0xC1FF2026 

0xC1FF2039 0xC1FF2027 

0xC1FF2040 0xC1FF2028 

0xC1FF2041 0xC1FF2029 







0xC1FF2048 0xC1FF2030 

0xC1FF2049 0xC1FF2031 







0xC1FF2064 0xC1FF2040 

0xC1FF2065 0xC1FF2041 

0xC1FF2066 0xC1FF2042 

0xC1FF2067 0xC1FF2043 

0xC1FF2068 0xC1FF2044 

0xC1FF2069 0xC1FF2045 

0xC1FF2070 0xC1FF2046 

0xC1FF2071 0xC1FF2047 

0xC1FF2072 0xC1FF2048 

0xC1FF2073 0xC1FF2049 



428 6875 9497–003





0xC1FF2080 0xC1FF2050 

0xC1FF2081 0xC1FF2051 

0xC1FF2082 0xC1FF2052 

0xC1FF2083 0xC1FF2053 

0xC1FF2084 0xC1FF2054 

0xC1FF2085 0xC1FF2055 

0xC1FF2086 0xC1FF2056 

0xC1FF2087 0xC1FF2057 

0xC1FF2088 0xC1FF2058 

0xC1FF2089 0xC1FF2059 







0xC1FF2096 0xC1FF2060 

0xC1FF2097 0xC1FF2061 

0xC1FF2098 0xC1FF2062 

0xC1FF2099 0xC1FF2063 

0xC1FF2100 0xC1FF2064 

0xC1FF2101 0xC1FF2065 

0xC1FF2102 0xC1FF2066 

0xC1FF2103 0xC1FF2067 

0xC1FF2104 0xC1FF2068 

0xC1FF2105 0xC1FF2069 







0xC1FF2112 0xC1FF2070 

0xC1FF2113 0xC1FF2071 

0xC1FF2114 0xC1FF2072 

0xC1FF2115 0xC1FF2073 

0xC1FF2116 0xC1FF2074 

0xC1FF2117 0xC1FF2075 

0xC1FF2118 0xC1FF2076 

0xC1FF2119 0xC1FF2077 

0xC1FF2120 0xC1FF2078 

0xC1FF2121 0xC1FF2079 







0xC1FF2128 0xC1FF2080 

0xC1FF2129 0xC1FF2081 

0xC1FF2130 0xC1FF2082 


6875 9497–003 429


0xC1FF2131 0xC1FF2083 

0xC1FF2132 0xC1FF2084 

0xC1FF2133 0xC1FF2085 

0xC1FF2134 0xC1FF2086 

0xC1FF2135 0xC1FF2087 

0xC1FF2136 0xC1FF2088 

0xC1FF2137 0xC1FF2089 





0xC1FF2144 0xC1FF2090 

0xC1FF2145 0xC1FF2091 

0xC1FF2146 0xC1FF2092 

0xC1FF2147 0xC1FF2093 

0xC1FF2148 0xC1FF2094 

0xC1FF2149 0xC1FF2095 

0xC1FF2150 0xC1FF2096 

0xC1FF2151 0xC1FF2097 

0xC1FF2152 0xC1FF2098 

0xC1FF2153 0xC1FF2099 







0xC1FF2160 0xC1FF20A0 

0xC1FF2161 0xC1FF20A1 

0xC1FF2171 0xC1FF20AB 

0xC1FF2172 0xC1FF20AC 

0xC1FF2173 0xC1FF20AD 

0xC1FF2174 0xC1FF20AE 

0xC1FF2175 0xC1FF20AF 

0xC1FF2176 0xC1FF20B0 







0xC1FF2192 0xC1FF20C0 









0xC1FF2202 0xC1FF20CA 

430 6875 9497–003

0xC1FF2203 0xC1FF20CB 

0xC1FF2204 0xC1FF20CC 

0xC1FF2205 0xC1FF20CD 

0xC1FF2206 0xC1FF20CE 

0xC1FF2207 0xC1FF20CF 

0xC1FF2208 0xC1FF20D0 






0xC1FF2221 0xC1FF20DD 

0xC1FF2222 0xC1FF20DE 

0xC1FF2223 0xC1FF20DF 

0xC1FF2224 0xC1FF20E0 










0xC1FF2234 0xC1FF20EA 

0xC1FF2235 0xC1FF20EB 

0xC1FF2236 0xC1FF20EC 

0xC1FF2237 0xC1FF20ED 

0xC1FF2238 0xC1FF20EE 

0xC1FF2239 0xC1FF20EF 

0xC1FF2240 0xC1FF20F0 










0xC1FF2250 0xC1FF20FA 

0xC1FF2251 0xC1FF20FB 

0xC1FF2252 0xC1FF20FC 

0xC1FF2253 0xC1FF20FD 

0xC1FF2254 0xC1FF20FE 

0xC1FF2255 0xC1FF20FF 

0xC1FF2256 0xC1FF2100 

0xC1FF2257 0xC1FF2101 

0xC1FF2258 0xC1FF2102 

0xC1FF2259 0xC1FF2103 

0xC1FF2260 0xC1FF2104 

0xC1FF2261 0xC1FF2105 

0xC1FF2262 0xC1FF2106 


6875 9497–003 431


0xC1FF2263 0xC1FF2107 

0xC1FF2264 0xC1FF2108 

0xC1FF2265 0xC1FF2109 


WIN-RPC 

Component: EIDL PRI-11433812 

Remove Client Fast Interface Key 

SYMPTOMS: 

Must have the WinRPC client fast interface key installed in order 

to use the client fast interface. 


Make the following changes to the WIN RPC Installation and 

Programming Guide (8808 0593): 

Add the following section to Section 9. Advanced Features: 

Client Fast Interface 

The client fast interface allows performance improvements 

for those clients which do not use any of the following 

features: 

- Association groups 

- Asynchronous calls 

- Automatic binding 

- Callbacks 

- Maybe calls 

- Multiple calls in progress at one time 

- UDP protocol 

How to Use the Client Fast Interface 

The user must modify the RPC library interface name defined 

within the stub to WINRPCCLIENTFI to use the client fast 

interface. There are several different ways in which the 

RPC library interface name can be modified. The code file 

can be WFL modified to file equate the interface name of 

the RPC library, the interface name of the RPC library can 

be file equated at run time or the user's application 

source can be modified to change the interface name 

programmatically. 

If the user chooses to modify the interface name within the 

source of their application, the modification must occur 

before calling the procedure RPC_Initialize_. 

This procedure performs the LINKLIBRARY call to RPC. 

If the call to LINKLIBRARY returns an error, the result will 

be returned to the user's application as the result of the 

RPC_Initialize_ procedure. The user's 

432 6875 9497–003


application should check the result of this procedure 

for errors. 

Algol Example: 

/* ACF file */ 

global [algol, rpc_client] 

[explicit_handle, protocol (tcp)] 

interface readfile 

{ 

. . . 

} 

/* IDL file */ 

[uuid (D37992BC-2AB8-4cb3-86E1-43BE026F74E4) 

,version (5.1) 

] 


{ 

. . . 

} 

% Client Program 

BEGIN 

$$ INCLUDE CLSTUB="WINRPC/MCP/EXAMPLE/READFILE/CLIENT/STUB. 

$$ INCLUDE CLSTUB="WINRPC/MCP/EXAMPLE/READFILE/CLIENT/BODY. 

REAL rslt; 

% Change the RPC interface name to use the client fast 

% interface. 

REPLACE RPC.INTERFACENAME BY 

"WINRPCCLIENTFI."; 

rslt := RPC_Initialize_readfile; 

. . . 

END. 

[ NOTE: ]] 

Component: RPC PRI-11433499 


SYMPTOMS: 









6875 9497–003 433



features: 




- Callbacks 

- Maybe calls 





















for errors. 






{ 

. . . 

} 




] 


{ 

. . . 

} 


BEGIN 



REAL rslt; 

434 6875 9497–003



% interface. 




. . . 

END. 

[ NOTE: ]] 



SYMPTOMS: 










features: 




- Callbacks 

- Maybe calls 



















6875 9497–003 435




for errors. 






{ 

. . . 

} 




] 


{ 

. . . 

} 


BEGIN 



REAL rslt; 


% interface. 




. . . 

END. 

[ NOTE: ]] 


Allow User To Stop/Start Endpoint Mapper Server 

SYMPTOMS: 

A denial of service attack can occur due to endpoint mapper offering 

well known port 135. The endpoint mapper server allows RPC clients 

to determine the port number currently assigned to a particular RPC 

server running on the MCP server. 


In the WIN RPC Installation and Programming Guide (8808 0593), add 

the following to Section 3. Operating Win RPC after the sub-section 

Restarting Endpoint Mapper: 

436 6875 9497–003


Start/Terminate Endpoint Mapper Server 

This command allows you to start or stop the Win RPC 

library's Endpoint Mapper server. The default value is STOP. 

This command does not affect the user's Win RPC servers running 

on the MCP server. 

Syntax 

-- NA -- WINRPC --+- EPM ------------+-+- START -+-+---------+--| 

|- ENDPOINTMAPPER -| |- STOP --| |- :SAVE -| 

Explanation 

ENDPOINTMAPPER START 

This option causes the Win RPC library's Endpoint Mapper server 

to run and offer well known port 135. 

ENDPOINTMAPPER STOP 


to stop so that well known port 135 will no longer be offered. 

When the Win RPC library's Endpoint Mapper server is stopped, 

the RPC client must specify the RPC server endpoint as it will 

not be able to query the Win RPC Endpoint Mapper server to get 

the endpoint as the Win RPC Endpoint Mapper server is no longer 

running. 

ENDPOINTMAPPER :SAVE 

This causes the value of ENDPOINTMAPPER of START or STOP to be 

saved across restarts of the Win RPC library. 

NOTE: 

If you have existing Win RPC servers running on the MCP server 

the clients will no longer be able to query the Win RPC Endpoint 

Mapper server to get the endpoint due to the default value of 

STOP. Enter the command NA WINRPC EPM START :SAVE to get back 

to the original behavior of the Win RPC Endpoint Mapper server. 


Allow User To Stop/Start Endpoint Mapper Server 

SYMPTOMS: 

A denial of service attack can occur due to endpoint mapper offering 

well known port 135. The endpoint mapper server allows RPC clients 

to determine the port number currently assigned to a particular RPC 

server running on the MCP server. 

6875 9497–003 437



In the WIN RPC Installation and Programming Guide (8808 0593), add 

the following to Section 3. Operating Win RPC after the sub-section 

Restarting Endpoint Mapper: 

Start/Terminate Endpoint Mapper Server 

This command allows you to start or stop the Win RPC 

library's Endpoint Mapper server. The default value is STOP. 

This command does not affect the user's Win RPC servers running 

on the MCP server. 

Syntax 

-- NA -- WINRPC --+- EPM ------------+-+- START -+-+---------+--| 

|- ENDPOINTMAPPER -| |- STOP --| |- :SAVE -| 

Explanation 

ENDPOINTMAPPER START 


to run and offer well known port 135. 

ENDPOINTMAPPER STOP 


to stop so that well known port 135 will no longer be offered. 

When the Win RPC library's Endpoint Mapper server is stopped, 

the RPC client must specify the RPC server endpoint as it will 

not be able to query the Win RPC Endpoint Mapper server to get 

the endpoint as the Win RPC Endpoint Mapper server is no longer 

running. 

ENDPOINTMAPPER :SAVE 

This causes the value of ENDPOINTMAPPER of START or STOP to be 

saved across restarts of the Win RPC library. 

NOTE: 

If you have existing Win RPC servers running on the MCP server 

the clients will no longer be able to query the Win RPC Endpoint 

Mapper server to get the endpoint due to the default value of 

STOP. Enter the command NA WINRPC EPM START :SAVE to get back 

to the original behavior of the Win RPC Endpoint Mapper server. 

438 6875 9497–003

© 2010 Unisys Corporation. 

All rights reserved. 

*68759497-003* 

6875 9497–003

ClearPath Enterprise Servers MCP Release DCL - Public Support ...

Create successful ePaper yourself

Delete template?

Save as template?