|
Results |
|
IOO compatibility with Tivoli Advanced Catalog Management
- BCS Force OPEN Failed after REORG. ... CAS Communications Failed - RC=8 RSN=00000000 CKM130F5E BCS(ICFCAT.CATSRC) VALIDATION FAILED on system QAS1. - BCS will remain LOCKED . ... QAS1 Primary ** VALIDATION FAILED ** ... | CKM130F5E BCS(bcs.name) VALIDATION FAILED on system xxxxxx. | CKM130F5W BCS(bcs.name) VALIDATION FAILED on system xxxxxx. ... | REORG Job that the BCS failed validation on that system. |
|
|
|
IOO Message ULTIM06E Load failed for ULTIGBnn
IOO Message ULTIM06E Load failed for ULTIGBnn
|
|
|
Top Secret: SZIST55W SAF extract failure followed by SZIST56W DMM feature disallowed so turned off
Top Secret: SZIST55W SAF extract failure followed by SZIST56W DMM feature disallowed so turned off
|
|
|
SZIST05E LOAD macro failure for C'ULTIGBL0',R15-R1=x'00000004 7FFFBD50 00000806'.
SZIST05E LOAD macro failure for C'ULTIGBL0',R15-R1=x'00000004 7FFFBD50 00000806'.
|
|
|
BMC108622W EXPANSION REQUEST FAILED,CPLRFDBK(10210010),DDNAME(BPLMST ). BCSS with IOO 3.1.5.01
BMC108622W EXPANSION REQUEST FAILED ,CPLRFDBK(10210010),DDNAME(BPLMST ). BCSS with IOO 3.1.5.01
|
|
|
U504 - SZI2SZI2 409EUOUF,F339S010, BBRP,R DMS-II positioning failure.
U504 - SZI2SZI2 409EUOUF,F339S010, BBRP,R DMS-II positioning failure .
|
|
|
IOO IMS jobs failing with U4083 abend in program CEEPLPKA at offset +07B642
IOO IMS jobs failing with U4083 abend in program CEEPLPKA at offset +07B642
|
|
|
S0C4 in ULTI020 in BMC CMF monitor
09.14.38 STC25185 BBDDA017I CMF MONITOR Online (5.8.00) Service Point Attach complete 09.14.38 STC25185 BBDDA035I Data Collector LOCK disabled by BBDTDCDL PARMLIB member 09.14.38 STC25185 BBMXCL36W Default Security Resource Definition BBDTRN used for CMF
|
|
|
TSO regions sizes unchanged due to missing TSONVRGN parameter in global table
DISPLAY FORMAT: K (K=KBYTES P=PERCENT) REGION SIZE 6976K 12100K BREAK OUT USER SUBPOOLS: _ ALLOCATED 1216K 20668K MEMORY OBJECTS: 0 NON-RGN UNALLOC 1556K 1575.3M
|
|
|
Questions on XML licensing and CSA
1) If a product using XML licensing encounters invalid license information, does it immediately fail or does it continue and try the alternatives? For
|
|
|