×
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.
On 17-Feb-2015 12:35 -0600, Steinmetz, Paul wrote:
<<SNIP>>
CPYFRMSTMF FROMSTMF('/QOPT/CDROM/Y2SYCBL.SAVF')
TOMBR('/QSYS.LIB/TEMP2E.LIB/Y2SYCBL.SAVF') MBROPT(*REPLACE)
<<SNIP>>
To copy binary data that is in save-file format from the noted\named
STMF [loaded in /QOPT] into the existing Device File of attribute SAVF
of the name Y2SYCBL in library TEMP2E [in /QSYS.LIB], the proper To
Member (TOMBR) specification had always been [and presumably is still]:
TOMBR('/QSYS.LIB/TEMP2E.LIB/Y2SYCBL.FILE')
In an old release [v5r3], the error msg CPFA0AE "An error occurred
while trying to resolve object name." was the expected effect, rather
than the error msg CPDA082 "Object is not a file or is a file with
attributes not supported by this command." The CPDA082 seems to imply
an existing object as identified by the specification in the TOMBR()
parameter already exists but is incompatible.?
The name specification using the extension\suffix of SAVF is AFaIK
only supported in the FTP; i.e. the FTP utility has enhanced support for
an extension specification, to allow something other than the
object-type, specifically\minimally for the SAVF variant of the *FILE
object. If the Copy From Stream File (CPYFRMSTMF) since had been
enhanced [in releases newer than effect seen described above], to
support that same naming variation supported by FTP, then perhaps the
issue that was encountered is that a *FILE of the name Y2SYCBL exists in
TEMP2E, but the file object is not a device file with the attribute SAVF.?
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.
midrange.com
