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



Going from Power8 to 6.1 In addition to the error below I also see
this error:
Message ID . . . . . . : CPF5739 Severity . . . . . . . : 40

Message type . . . . . : Diagnostic

Date sent . . . . . . : 12/22/17 Time sent . . . . . . :
11:39:26


Message . . . . : Cannot assign or release DDM file(s).

Cause . . . . . : This system or the target Distributed Data
Management
(DDM) system detected a condition that caused the assign or release
request
to fail.

Recovery . . . : See the previous messages in the system log to
analyze the
conditions that caused the failure. Make the needed corrections, and
then
try the request again.






I did try something different and did get a message I cannot
understand I tried using DDMF going the other way
Power8 to 6.1 machine

And I got an error: (that points me to X'1443' - Now to figure out
what the cause for X'1443" means (Looking for DDM Architecture
Reference)


Message ID . . . . . . : CPF3E01 Severity . . . . . . . : 40

Message type . . . . . : Information

Date sent . . . . . . : 12/22/17 Time sent . . . . . . :
11:39:26


Message . . . . : DDM parameter value not supported.

Cause . . . . . : A value was sent from the client that is not
supported by
this server. The following are not supported (See X'1443'):

-- '1144'X or '212D'X -- Version names.

-- '2106'X -- Decimal precision of 15.

-- '2112'X -- Package names or collection identifiers greater than
10
characters in length.

-- '2128'X -- Collection identifiers greater than 10 characters in
length.
-- '2129'X -- Release of allocated resources at conversation
deallocation.
IBM i supports release of resources only after commit.

-- '2130'X -- Option to explain information about SQL statements.

-- '2131'X -- User IDs greater than 10 characters in length.

Recovery . . . : Change the value sent by the client and try the
operation
again.

Technical description . . . . . . . . : If DDM code point X'1443'
does not
appear in the list above refer to the DDM Architecture Reference for
more
information.





-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
John Allen
Sent: Friday, December 22, 2017 11:31 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: DDMF work for WRKF does not work for CPYSRCPF

Nope

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Rob Berendt
Sent: Friday, December 22, 2017 11:32 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: DDMF work for WRKF does not work for CPYSRCPF

Does "read" work?
DSPPFM FILE(QTEMP/GDI) MBR(AAA)
on an existing member?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "John Allen" <jallen@xxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 12/22/2017 11:29 AM
Subject: RE: DDMF work for WRKF does not work for CPYSRCPF
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



My bad 9Typo) I was using CPYSRCF
I also tried CPYF

Still Nothing


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Rob Berendt
Sent: Friday, December 22, 2017 8:28 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: DDMF work for WRKF does not work for CPYSRCPF

Vernon,

I see the mention of the mythical command CPYSRCPF in the subject line
of this thread now. Interesting, I have no such command.
However I figured that maybe this was a PDM thing. So I prompted a 3
copy. Oh, it's not cpysrcPf. It's simply cpysrcf.

CPYSRCF FROMFILE(ROB/QPGMSRC) TOFILE(QTEMP/GDI) FROMMBR(AAA) DDM
object GDI in QTEMP uses remote object ROB/QPGMSRC.
Member AAA added to file GDI in QTEMP.
DDM object GDI in QTEMP uses remote object ROB/QPGMSRC.
DDM object GDI in QTEMP uses remote object ROB/QPGMSRC(AAA).
79 records loaded to member AAA file QPGMSRC in library ROB.
79 records copied from member AAA.

If there still is a cpysrcPf command from some other toolset then, no,
I've not tried that.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 12/22/2017 08:05 AM
Subject: Re: DDMF work for WRKF does not work for CPYSRCPF
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Hi Rob

I did wonder about which command the OP used to copy the source file -

the OP said CPYSRCPF - CPYF works, as you show here - have you tried
CPYSRCPF?

Merry Christmas and many regards!
Vern

On 12/22/2017 6:32 AM, Rob Berendt wrote:
CRTDDMF FILE(QTEMP/GDI) RMTFILE(ROB/QPGMSRC) RMTLOCNAME(gdi *IP)
File
GDI created in library QTEMP.

CPYF FROMFILE(ROB/QPGMSRC) TOFILE(QTEMP/GDI) FROMMBR(A) TOMBR(A)
MBROPT(*REPLACE)
Member A added to file GDI in QTEMP.
235 records copied from member A.


Rob Berendt

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: http://amzn.to/2dEadiD


--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: http://amzn.to/2dEadiD


--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


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.