Re: V7R1 CL compile failing for CPYTOIMPF when specifying Target release *PRV -- MIDRANGE-L

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

Paul:

The CPYTOIMPF command did not have an "ORDERBY" parameter at V6R1 or before that. That was added at V7R1, and perhaps even not added until one of the "Technical Refresh" levels after V7R1 was released (because when I prompt CPYTOIMPF at V7R1 and press F10=Additional parameters, and put the cursor in the "ORDERBY" field and press F1=Help, it says "Help not available.").

So, your CL program will not compile with TGTRLS(*PRV) unless you omit the "ORDERBY(*ARRIVAL)" specification.

Cheers,

Mark S. Waterbury

> On 12/26/2013 7:29 PM, Steinmetz, Paul wrote:

V7R1 CL compile failing for CPYTOIMPF when specifying Target release . . . . . . . . . *PRV
Compiles fine if Target release current.
Any known issues with Target release *PRV.

2300- CPYTOIMPF FROMFILE(*LIBL/ME5PHY01) TOSTMF(&IFSFILE) +
2400 MBROPT(*REPLACE) FROMCCSID(37) +
2500 STMFCODPAG(*PCASCII) STMFAUT(*INDIR) +
2600 RCDDLM(*CRLF) DTAFMT(*DLM) STRDLM(*NONE) +
2700 RMVBLANK(*NONE) FLDDLM(*TAB) +
2800 ORDERBY(*ARRIVAL)
* CPD0043 30 Keyword ORDERBY not valid for this command.

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.