× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



*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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.