Re: CPFA09E not recoginzed by MONMSG -- MIDRANGE-L

Subject: Re: CPFA09E not recoginzed by MONMSG
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Mon, 30 Jun 2008 11:28:27 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Marchini, Richard wrote:

I know the Help Text for the Copy Object command (COPY) doesn't list
CPFA09E as one of the errors, I can only surmise that it was added as an
error after the Help Text was written.

I based my statement on the V5R3 help text for the CPY command ... and I just checked V6R1 and CPFA09E isn't listed there either.

If this is more than is supposed to be included in these mailing list
emails, I apologize. I'm just at my wit's end trying to unravel this. By
the way, the SBMJOB parameters for these two jobs are identical.

Is there any significant difference in how the CPY command is being invoked? Are you using wildcards on the copy?

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: CPFA09E not recoginzed by MONMSG , Marchini, Richard
Re: CPFA09E not recoginzed by MONMSG , rob

This mailing list archive is Copyright 1997-2025 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.