Changed the subject header ---------- Forwarded message ---------- From: Jake anderson <[email protected]> Date: Mon, Apr 2, 2012 at 12:10 PM Subject: Re: Initialize Tape Options To: IBM Mainframe Discussion List <[email protected]>
Hi Mike, I get the same error message using with below JCL Jake On Mon, Apr 2, 2012 at 10:46 AM, Mike Schwab <[email protected]>wrote: > I see some differences between your jcl and IBM's examples. > Why don't you try IBM's values? > Probably don't need the DEN value, or the LABEL that you supplied. > > > http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.idau100%2Fdgt2u16018.htm > > Example 1: Write EBCDIC Labels on Three Tapes > > z/OS V1R12.0 DFSMSdfp Utilities > SC26-7414-07 > > In this example, serial numbers 001234, 001235 and 001236 are placed > on three tape volumes. The labels are written in EBCDIC at 800 bits > per inch. Each volume labeled is mounted, when it is required, on a > single 9-track tape unit. > > //LABEL1 JOB ... > //STEP1 EXEC PGM=IEHINITT > //SYSPRINT DD SYSOUT=A > //LABEL DD DCB=DEN=2,UNIT=(tape,1,DEFER) > //SYSIN DD * > LABEL INITT SER=001234,NUMBTAPE=3 > /*The control statements are as follows: > > LABEL DD defines the tape unit used in the labeling operation. > SYSIN DD defines the control data set, which follows in the input stream. > LABEL INITT specifies the number of tapes to be labeled (3), beginning > with 001234. > > > > On Sun, Apr 1, 2012 at 11:16 PM, Jake anderson <[email protected]> > wrote: > > Dear All, > > > > Reason for opting another option to initialize was due to the below > abend : > > > > SYSTEM SUPPORT UTILITIES IEHINITT > >>> > >> > >> TAPE INITT SER=Z9BQB1 > >>> 00070000 > >> > >> IEH627I VOLUME NOT LABELED , REASON CODE = 00001000. REFER TO MESSAGE > >>> MANUAL FOR FOR EXPLANATION OF BIT SETTINGS > >> > >> IEH605I INVALID DEVICE ALLOCATED ON D72D > >>> > >> > >> IEH607I ALLOCATED DEVICES EXHAUSTED > >> > >> > > JCL : > > > > //TAPEINIT JOB MSGCLASS=X,MSGLEVEL=(1,1),CLASS=T, > > // NOTIFY=&SYSUID > > //STEP1 EXEC PGM=IEHINITT > > //TAPE DD UNIT=890,LABEL=(1,SL) > > //SYSPRINT DD SYSOUT=* > > //SYSIN DD * > > TAPE INITT SER=Z9BQB1 > > > >> ] > >> > >> > > > >> > >> > >> > > Z/os : 1.8 > > > > Lookat explanation : > > > > Explanation: > > > > The volume was not labeled as a result of exit processing. The reason for > > the failure is encoded (hex representation) in the reason code, which > maps > > directly to the settings in the four-byte field INXNLBRS in macro > IEHUEXIT, > > which normally resides in SYS1.MACLIB. The macro should be referenced for > > the very latest mapping. However, the bit definitions current at the time > > of this edition are: > > Byte 1 ww X'80' Error on call to CSVDYNEX. X'40' An exit routine > abended. > > X'20' Invalid return code from exit routine (not 0, 4, 8). X'10' Invalid > > reason code from exit routine (not 0, 4). X'08' A previous exit indicated > > that the volume is not to be labeled. X'04' Conflicts in the results from > > calls to exits have been encountered. X'02' At least one exit routine > > returned rc=0 with a modified volser and either other exit routines > > returned rc=0 without modifying the volser, or the modified volser's > didn't > > match. X'01' Two or more exits requested that the volser be changed, but > > the changed volsers don't match. Byte 2 xx X'80' An exit routine > > requested no OWNERID change, but another exit requested an OWNERID > change. > > X'40' Two or more exits requested that the OWNERID be changed, but the > > changed OWNERIDs don't match. X'20' An exit routine requested no ACCODE > > change, but another exit requested ACCODE change. X'10' Two or more exits > > requested that the ACCODE be changed, but the changed ACCODEs don't > match. > > X'08' A conflict in the return codes returned by the exit routines was > > detected. One routine returned a 0 and another returned an 8. X'04' > Invalid > > volser character supplied by an exit routine. X'02' Invalid OWNERID > > character supplied by an exit routine. X'01' Invalid ACCODE character > > supplied by an exit routine. Byte 3 yy X'80' There is a conflict in > rc=8 > > reason code processing. An exit routine returned rsn=4, requesting > remount > > and another returned rsn=0, indicating don't label the tape at all. > X'40' An > > exit routine requested remount but no new volser was provided. X'20' > Conflict > > in remount volser value. New volser values don't match. X'10' Failure in > > internal processing not related to dynamic exits services. X'08' Operator > > replied to skip labeling the volume. X'04' Mounted volume is file > > protected. X'02' Reserved. X'01' Reserved. Byte 4 zz X'FF' Reserved. > > System action: > > > > Processing will continue with next INITT control card, if possible. > > Conditions such as failures in the CSVDYNEX facility will prevent > > continuation. > > Operator response: > > > > None. > > System programmer response: > > > > A System Programmer may need to investigate some failures, particularly > > those associated with the CSVDYNEX facility itself. Other failures that > may > > require such attention would be those associated with conflicts between > > exit routines. > > > > > > Is there anyone who has faced this similar issue at your shops ? > > > > > > Jake > > > > On Mon, Apr 2, 2012 at 7:38 AM, Russell Witt <[email protected]> > wrote: > > > >> Kees, > >> > >> Actually, the CA-1 utility does not invoke IEHINITT. After doing the > >> administration (validating the tape is in scratch status), we re-write > the > >> VOL1/HDR1 records with the defined volser. And there is an option to do > a > >> secure erase of the remainder of the tape if desired (though for a 3590 > >> that > >> might take a while). > >> > >> Russell Witt > >> CA 1 L2 Support Manager > >> > >> -----Original Message----- > >> From: IBM Mainframe Discussion List [mailto:[email protected]] On > >> Behalf > >> Of Vernooij, CP - SPLXM > >> Sent: Sunday, April 01, 2012 3:30 AM > >> To: [email protected] > >> Subject: Re: Initialize Tape Options > >> > >> CA1 has its own tape init utility, but I won't be surprised if this is > >> IEHINIT plus some CA1 administration. > >> > >> Kees. > >> > >> "Jake anderson" <[email protected]> wrote in message > >> news:<CAHTvvRWZEbxVF-b+HH3TOzBMGPVKQv7c4F= > [email protected] > >> >... > >> > Hello List, > >> > > >> > Good Morning ! > >> > > >> > Apart from IEHINIT, are there any freeware or any available utility to > >> > initialize the 3590 tape ? This is just a general question out of > >> curiosity > >> > :). > >> > > >> > My environment : > >> > > >> > Z/os : 1.8 > >> > > >> > Jake > >> > > >> > >> ---------------------------------------------------------------------- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to [email protected] with the message: INFO IBM-MAIN > >> > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > -- > Mike A Schwab, Springfield IL USA > Where do Forest Rangers go to get away from it all? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
