Re: CPYFRMIMPF ERRRCDFILE

Thanks Chuck.

I got hung up on the syntax. Mistake I made was trying to make one
parameter - since that was what I thought I saw when I prompted the
command and then did F14.

My trip-up was with the slash between library and file. Member just
added to the brew.

John McKee

On Tue, Aug 7, 2012 at 5:52 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:

Each name in both the qualified [by library or library search special
value] and unqualified name needs to be specified as variable [e.g.
CPYFRMIMPF ERRRCDFILE(&L/&F &M)], or the completed\concatenated
command-string must be passed to a command shell\interpreter [e.g. CALL
QSYS/QCMDEXC PARM(&ImportRqs &RqsStrLen)]

When one CL variable is incorrectly used to represent all three
values in a CLP invocation of the command, the effect of variable
replacement for the command request would be something like
ERRRCDFILE('a_single_string_trunc') for which an error such as CPD0078
"Value 'a_single_s' for parameter ERRRCDFILE not a valid name." would
diagnose the incorrect usage.

Regards, Chuck

On 07 Aug 2012 14:41, John McKee wrote:

I know I saw this maybe three weeks ago.

Command has a single parameter used for library, file, and member.
How are they specified in a CL as variables?

Specifically, when viewed with F14:

CPYFRMIMPF ... ERRRCDFILE(LIB/FILE MBR)

But, when I try to build that string in CL, the program ends. Says
library/file is incorrect. The value in the dump shows library a
slash, and the member - but truncated. Obviously too long.

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