RE: QCLSRC with PF38-SRC attribute -- MIDRANGE-L

So you've already converted all your source code and only want to change the file attributes of QCLSRC and QDDSSRC from PF38-SRC to PF-SRC?

I guess I don't see any major issue if this is all you want to do.

Simply create QCLSRC and QDDSSRC in a different library (without the PF-38-SRC attribute), copy your source to the new files, delete the PF38-SRC files and move the new QCLSRC and QDDSSRC files back to the original library. It may take you an hour at most.

CPYF FROMFILE(yourS38lib/QCLSRC) TOFILE(yournewlib/QCLSRC) FROMMBR(*ALL) TOMBR(*FROMMBR) MBROPT(*REPLACE) FMTOPT(*NONE)

CPYF FROMFILE(yourS38lib/QDDSSRC) TOFILE(yournewlib/QDDSSRC) FROMMBR(*ALL) TOMBR(*FROMMBR) MBROPT(*REPLACE) FMTOPT(*NONE)

The above commands will copy all your source members from one library to another.

Use the MOVOBJ command to move yournewlib/SourceFile back to yourS38lib once you've deleted yourS38lib/QCLSRC and yourS38lib/QDDSSRC files.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Thursday, January 24, 2013 9:09 AM
To: Midrange Systems Technical Discussion
Subject: RE: QCLSRC with PF38-SRC attribute

We have no S/38 file types. We did get rid of those long ago.

We only have a source file with a PF38-SRC Attribute

Opt Object Type Attribute
INCLUDE *FILE PF-SRC
PROTOTYPE *FILE PF-SRC
QCLSRC *FILE PF38-SRC
QCMDSRC *FILE PF-SRC
QDDSSRC *FILE PF38-SRC

Member Type
ACKTIM PF
ACLCATCD LF
ACLCAT01 LF
ACLCAT04 LF
ACLDETAL LF
ACLDETCU LF
ACLDET03 LF

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Monnier, Gary
Sent: Thursday, January 24, 2013 11:49 AM
To: Midrange Systems Technical Discussion
Subject: RE: QCLSRC with PF38-SRC attribute

As far as I know files you are going to have to convert manually somehow. Something like...

1. Create a new library to hold all S/38 file objects.
2. Move your S/38 files to the new library.
3. Recreate the files after removing the -38 from the source.
4. CPYF S/38 files to recreated files.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Thursday, January 24, 2013 8:23 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: QCLSRC with PF38-SRC attribute

We did that a long time ago. All RPG is RPGLE and all most CL is CLLE. None of the DDS has "38" as a Type. Its only at the overall file level that the attribute needs changed

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Thursday, January 24, 2013 11:15 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: QCLSRC with PF38-SRC attribute

Mike,

Have you resolved the issue related to the S/38 and CPF using dots between the object name and the library name? That's one thing you should address as soon as possible.

That being said, your idea of the rename and copy is certainly valid.

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Thursday, January 24, 2013 9:53 AM
To: Midrange Systems Technical Discussion
Subject: QCLSRC with PF38-SRC attribute

This is going to date us for how long we have been on this platform. Our QCLSRC and QDDSSRC files have an attribute of PF38-SRC. This attribute setting is preventing us from using Rational to edit the source. What's going to be the best way to get rid of that attribute? You can't just change it. There is no command to do that. So we are thinking rename QCLSRC to something else, create a new QCLSRC then copy every member over to the new file. 2,076 members in QCLSRC and 13,304 members in QDDSSRC. Would anyone have any other options to make this change?
--
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.

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

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

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

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