BrightStor CA-1 Tape Management - SupportConnect

More documents

Recommendations

Info

*** TESTRDS NOT VALID WITH DSNBS, TEST AND NODEFLTExplanation : TESTRDS parmameter is not valid with these parms.User Reponse: Correct the JCL and resubmit the job.*** SELECT AND JOB ARE MUTUALLY EXCLUSIVEExplanation : The SELECT and JOB keywords can not be specified in the same retention statement.User Reponse: Correct the retention statement(s) and resubmit the job.*** PARSE ERRORExplanation : This statement has invalid syntax or missing/extra keywords.User Reponse: Correct the retention statement(s) and resubmit the job.*** PARSE ERROR IN ABEND KEYWORDExplanation : This statement has invalid syntax or missing/extra keywords.User Reponse: Correct the retention statement(s) and resubmit the job.*** PARSE ERROR IN LABEL KEYWORDExplanation : This statement has invalid syntax or missing/extra keywords.User Reponse: Correct the retention statement(s) and resubmit the job.*** MGMTCLAS=, M= DSN=, AND D= ARE MUTUALLY EXCLUSIVEExplanation : This statement contains keywords or forms of keywords which cannot be specifiedtogetheron an RDS statement.User Reponse: Correct the retention statement(s) and resubmit the job.*** JOBNAME=, JOB= and J= ARE MUTUALLY EXCLUSIVEExplanation : This statement contains multiple forms of the same keyword.User Reponse: Correct the retention statement(s) and resubmit the job.*** PROGRAM ABORTED FOR FATAL PARSE ERRORExplanation : The program encountered error(s) while parsing a RDS statement that were so severe thatthe program could not identify the error or continue processing.User Reponse: Correct the retention statement(s) and resubmit the job.PDC# QI32727
BrightStor CA-1 Product Documentation ChangePDC# QI35237DATE: March 5, 2003RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoSUBJECT: Enhancement of Pointer Verification Utility TMSPTRSDESCRIPTION/DISCUSSION:This Product Documentation Change (PDC) describes the changes to TMSPTRS introduced by BrightStorCA-1 APAR QO35140:• Support of a blocked SYSUT3 data set• Elimination of all device dependent code• Support of SYSUT3 synchronization from the Audit data set (without• PARM=ENQ specified) with unlike device types• Handling of Sort errors• Modification of the ERR85 message text• Elimination of unneeded report trailerThese enhancements have been published as APAR QO35140 and will also be included in Service Pack 5of Brightstor CA-1 Release 5.2.TMSPTRS uses a work data set specified as SYSUT3 DD. It holds a copy of the TMC catalog and is usedfor the actual validation of multivolume and multi-data set chains. This SYSUT3 data set can now beblocked to save disk space. The BLKSIZE may be any multiple of the LRECL, 340, and does not dependon the block size of the active TMC.Performance can also be improved by allocating the SYSUT3 data set in VIO storage. Any DASD or VIOdevice may be used without limitation.It is now possible to allocate SYSUT3 on a device which differs from the device type of the TMC, evenwithout specifying PARM=ENQ. This allows TMSPTRS to copy the TMC and to synchronize the copy fromthe Audit data set without issuing a RESERVE against the TMC. A U0999-04 abend is no longer issued ifunlike device types are found.If the internal sort of the DSNB records is not successful, TMSPTRS now displays the sort return code andterminates with CC=16:"RETURN CODE xxx FROM SORT - PROCESSING TERMINATED".The message text of ERR85, "VOLUME xxxxxx HAS A CONFLICT BETWEEN FLAG4 (TMACVOLI) ANDACTVOL" was expanded to read: "VOLUME xxxxxx HAS A CONFLICT BETWEEN FLAG4 (TMACVOLI)OR FLAG5 (TMVTEXP) AND ACTVOL". Since the ACTVOL field can also be used to save the volser ofthe physical container volume of an exported virtual tape, ERR85 may also indicate a conflict betweenACTVOL and bit TMVTEXP of FLAG5, the "virtual volume exported" indicator. The ACTVOL field shouldPDC# QI35237
Page 1 and 2: BrightStor® CA-1® Tape Management
Page 5 and 6: COMPUTER ASSOCIATES INTERNATIONAL,
Page 7: • Data Erase UtilityA new Data Er
Page 10 and 11: Drop Support Date for Release 5.2:C
Page 12 and 13: This utility accepts input either v
Page 14 and 15: After all volumes have been written
Page 16 and 17: In this example, logical volumes LV
Page 18 and 19: QUERY COMPLETE, VOLUME IN ROBOT - A
Page 21 and 22: BrightStor CA-1 Product Documentati
Page 23 and 24: Note that a meaningful compression
Page 25 and 26: Replace line-----------------------
Page 27: with the following:----------------
Page 30 and 31: 1.28.3.1 Job Control Statements//st
Page 34 and 35: show a volser if either the TMACVOL
Page 36 and 37: User response: If this is an AIVS v
Page 38 and 39: CA-1 Retention data set Rules (Opti
Page 40 and 41: Specification:If set to YES, the Cn
Page 42 and 43: Or no valid input command was found
Page 44 and 45: Thank you for your continued suppor
Page 46 and 47: For example, if volume 123456 is de
Page 48 and 49: CONCLUSION:In addition to these opt
Page 50 and 51: • TMSBLDVRThis section documents
Page 52 and 53: 4. TMSBINQ, the online TMSTIQ displ
Page 54 and 55: FOLLOW UP PROCEDURES AFTER INITIAL
Page 56 and 57: Appendix A., TMC Volume Definition
Page 58 and 59: User Response: None. Information on
Page 60 and 61: TMSXT05I ATTACH TMSBLDVR TO COPY/EX
Page 62 and 63: User Response: None. Information on
Page 64 and 65: TMSXT80E COULD NOT OBTAIN TMSVOLU T
Page 66 and 67: 52 82 EXTEND ALREADY ACTIVESee msg
Page 68 and 69: TMS REPORT-80 Report Field Definiti
Page 70 and 71: TMS REPORT-81 Report Field Definiti
Page 72 and 73: Eyy-112 I/O ERROR ON TMCExplanation
Page 74: (29 CPU entries in same format not

BrightStor CA-1 Tape Management - SupportConnect

Create successful ePaper yourself

Delete template?

Save as template?