×
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 14:26 -0600, Steinmetz, Paul wrote:
On Tuesday, February 17, 2015 3:01 PM CRPence wrote:
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>>
<<SNIP>> the proper To Member (TOMBR) specification had always been
[and presumably is still]:
TOMBR('/QSYS.LIB/TEMP2E.LIB/Y2SYCBL.FILE')
<<SNIP>>
SAVF does exist.
Y2SYCBL *FILE TEMP2E SAVF
But was the TOMBR() specification on the failing request /corrected/
to use the expected .FILE naming instead of the unsupported [except at
least, in FTP] .SAVF naming?
Regardless of whatever might be the source of the trouble with using
the CPYFRMSTMF, a circumvention should be to use either of:
• the binary FTP [PUT or GET to name with the file naming extension
.SAVF per msg TCP12C7], e.g. the following PUT subcommand:
put /QOPT/CDROM/Y2SYCBL.SAVF /QSYS.LIB/TEMP2E.LIB/Y2SYCBL.SAVF
• the following Copy (CPY) CL command request:
CPY OBJ('/QOPT/CDROM/Y2SYCBL.SAVF')
TOOBJ('/qsys.lib/crp2.lib/savf.file')
DTAFMT(*BINARY) REPLACE(*YES)
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.