RE: CPYFRMIMP / CPYTOIMP

["Forbes, Vincent" <Vincent.Forbes@xxxxxxxx>]

Chris

It was a "Production" problem & I had to call IBM.  This command did not
show up in our V5R3 testing on our Dev box.  Both solutions worked for us
here, the first as an immediate fix & the second after we tested it on DEV.

\Vincent

 -----Original Message-----
From:   Chris Bipes [mailto:chris.bipes@xxxxxxxxxxxxxxx] 
Sent:   December 6, 2004 3:40 PM
To:     'Midrange Systems Technical Discussion'
Subject:        RE: CPYFRMIMP / CPYTOIMP

Thank you, thank you, thank you!  We had the first PTF, SI14126 installed
already so I created the data area and all works.  Gee the cover letter does
not mention anything about the data area.  Where or how did you find this
out?

Chris Bipes 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Forbes, Vincent
Sent: Monday, December 06, 2004 11:37 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: CPYFRMIMP / CPYTOIMP

Chris

I had a similar problem.  There are two options.

1.  This is a temp fix that causes the CPYFRMIMP command to use the V5R2
version.
1)      Apply ptf SI14126
2) CRTDTAARA DTAARA(QSYS/QCPFRMIMPF) TYPE(*CHAR) LEN(6) VALUE('CPV5R2')

2.
PTF SI16043 as a perm fix.  The data area above would need to be deleted
before the PTF is applied.
--
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.