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


  1.  Home
  2. MIDRANGE-L
  3. April 2009

Re: SRCPF record format name

"Change Management..." that may be where the hardcoding is going
on for the QCLSRC record format...
Jim


----- Original Message ----- From: "Paul Nelson" <nelsonp@xxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, April 10, 2009 4:23 PM
Subject: RE: SRCPF record format name


Apparently it is part of what they're doing. At any rate, it's outside the
norm of "best practices". If IBM can't help him, it's a self inflicted
wound.

He's worried about causing some sort of verification error in his change
management software, if he copies the source members into a properly created
file. I told him to set up a job over the weekend to re-promote and
re-deploy those problem objects, and his issue will go away.

Have a safe weekend.

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


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
Sent: Friday, April 10, 2009 3:01 PM
To: Midrange Systems Technical Discussion
Subject: RE: SRCPF record format name

all of my development is ILE (yes using named activation groups, etc.)
i've never had the compiler balk on a source file. heck it doesn't even
check the record format of the source PF, it's got to be something in the
setup for the compile. is it possible for you to post the error from the
job log after the botched compile? that's where the info will be for the
binding error (why the heck they don't put this info in the compile
listing is beyond me...)

Thanks,
Tommy Holden



From:
"Paul Nelson" <nelsonp@xxxxxxxxxxxxx>
To:
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Date:
04/10/2009 02:51 PM
Subject:
RE: SRCPF record format name
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



That's what I said, but apparently something is burping over the record
format name when it gets to the binding process.

This is why I avoid ILE. :-))

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


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
Sent: Friday, April 10, 2009 2:32 PM
To: Midrange Systems Technical Discussion
Subject: Re: SRCPF record format name

i just have to say...HUH? that doesn't make any sense, the compiler
doesn't care what the source file name, etc is...at all. it has to be
something in the code. perhaps they are using DCLF and specifying a
record format that doesn't exist or something?

Thanks,
Tommy Holden



From:
"Paul Nelson" <nelsonp@xxxxxxxxxxxxx>
To:
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Date:
04/10/2009 02:26 PM
Subject:
SRCPF record format name
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



List,

Anybody know to change the record format name within a SRCPF? A client
copied QRPGSRC and called it QCLSRC, and when they are trying to CRTBNDCL,
they are getting a record format name error.

I told him I'd ask the list, but that he should call IBM also.

Thanks

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



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




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.