× 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.



Very cool, man!!

On 2/17/2015 5:46 PM, Steinmetz, Paul wrote:
Vern,

That worked, thanks

CPY OBJ('/QOPT/CDROM/Y2SYCBL.SAVF') TOOBJ('/qsys.lib/temp2e.lib/y2sycbl.fi
le') TOCCSID(37) DTAFMT(*BINARY) REPLACE(*YES)
Ownership of object Y2SYCBL in TEMP2E type *FILE changed.
File Y2SYCBL created in library TEMP2E.
Ownership of object Y2SYCBL in TEMP2E type *FILE changed.
Object auditing value changed for Y2SYCBL in TEMP2E type *FILE.
Object copied.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Tuesday, February 17, 2015 6:43 PM
To: Midrange Systems Technical Discussion
Subject: Re: Extracting from a single iso loaded to an image catalog

Paul

Prompt the CPY command - you'll see a couple CCSID parameters. Change the TOCCSID to 37, I believe - that's what SAVFs will use.

The fact that FTP can use the SAVF extension is an accident or a gift, depending on your point of view. It is not what happens on the system - only in FTP.

HTH
Vern

On 2/17/2015 5:20 PM, Steinmetz, Paul wrote:
Chuck,

put /QOPT/CDROM/Y2SYCBL.SAVF /QSYS.LIB/TEMP2E.LIB/Y2SYCBL.SAVF
was successful.

CPY OBJ('/QOPT/CDROM/Y2SYCBL.SAVF')
TOOBJ('/qsys.lib/temp2e.lib/y2sycbl.f
ile') DTAFMT(*BINARY) REPLACE(*YES)
The CCSID of the target file could not be set to match the CCSID of the
source file.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
CRPence
Sent: Tuesday, February 17, 2015 4:49 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Extracting from a single iso loaded to an image catalog

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)

--
Regards, Chuck
--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.