|
How about posting the code that gets the message and loads the reply? It is possible that the specific message description used has changed, or that it was also lost when the upgrade happened. Have you run the code in debug and looked to see what is happening? Take care. On 10/3/06, Sivakumar Kanagavel <srkas400@xxxxxxxxx> wrote:
Yes. we are storing the available tape drives names in the data area and once the point of backup is reached, send a message to the operator using SNDUSRMSG to load the tape drives and specify its name. In the VALUES section of the command we specify all the valid tape drive names. Once the tape drive name is entered, use CPYTPTAP to save the file information. This was the exact code: CPYTOTAP FROMFILE(&lib1/&file1) > TOFILE(QTAPE) TOSEQNBR(*END) TOLABEL(&savefile1) TODEV(&tape1) > TOENDOPT(*LEAVE) TOEXPDATE(*PERM) The reply from the operator is stored in the variable &tape1. &tape1 shows as *N in the joblog though the operator replied some tape drive names. rob@xxxxxxxxx wrote: *N is no longer an option on V5R4. On V5R4 you have to enter a device or *TAPF. *TAPF will use the device specified in the tape file description. The reason it defaults to that in the first place is that you can do a CHGTAPF FILE(QTAPE) DEV(TAP01) and change it from the default of *NONE to an existing device. Now I don't know what the common practice is out there. I suspect it's one of two options. One either do a CHGTAPF or specify the device in the CPYTOTAP. Sounds like your shop had a standard to do a CHGTAPF. Now, since you have to change all of your CL, is a time to re-evaluate. If you want to bandage that you could create your own custom CPYTOTAP command, put it in a custom library and put that custom library tops in your system library list. In your custom command have it execute the QSYS/CPYTOTAP command but change the *N to *TAPF. Or, instead of *TAPF have it go to the device there also. Then again, you may not. Then if you do a CHGTAPF also to support those using *TAPF you'll have to modify the custom command also when you change from TAP01 to TAP02. Me, I'd change to the device name in the CL. Now, if you have multiple CL names I'd store the device name in a dataarea, retrieve that, and use that in the CPYTOTAP. Understand? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Sivakumar Kanagavel Sent by: midrange-l-bounces@xxxxxxxxxxxx 10/03/2006 01:18 PM Please respond to Midrange Systems Technical Discussion To Midrange Systems Technical Discussion cc Subject Re: CPF4116 Thanks for your reply. The Intresting part is the same code ran fine before we converted into I5/95 v5r3. One another thing puzzles me is if a message prompts asking for the the tape device to be mentioned and if operators reply with a device name, it defaults to '*N'. I am confused as it should take the repply as TAPE01, TAPE02 or whatever to TODEV. Can someone pls clarify why the system defaults to '*N"?. Tom Jedrzejewicz wrote: You are trying to copy a file to a tape device, but are not specifying a tape device. A specific tape device needs to be identified ... 1. on the CPYTOTAP command itself *OR* 2. through an OVRTAPF prior to the CPYTOTAP *OR* 3. by changing the QTAPE device file to have a specific tape drive assigned HTH, although I am not optimistic. -- Tom Jedrzejewicz tomjedrz@xxxxxxxxx On 10/2/06, Sivakumar Kanagavel wrote: > > Hi, > Could someone please advise me what is the reason for the following > error message. > > Message . . . . : No device defined for file QTAPE in library QGPL. > Cause . . . . . : An attempt was made to open a non-spooled device file > with > no device. Recovery . . . : Use the correct Change or Override > command to > either specify a device on the DEV parameter or specify SPOOL(*YES). > > > This is command failing in my program > > Message . . . . : 17800 - CPYTOTAP FROMFILE(MYLIB1/MYFIL1) > TOFILE(QTAPE) TOSEQNBR(*END) TOLABEL('MYFILE100') TODEV(*N) > TOENDOPT(*LEAVE) TOEXPDATE(*PERM) > > Any help in this is greatly appreciated. Thank you! > > -Sivakumar Kanagavel. > > -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. --------------------------------- Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.