I agree with retiring the home grown command. That being said, in order to
keep the auditors off your back, check out all the objects containing the
command to a new task. Use option 14 to compile everything in the task, and
then promote the task through the development cycle. When all have been
tested, promote and deploy the task to production.
It's much simpler to perform these actions on a task than to do each object
individually.
Also, give consideration to upgrading to version 8.2 of Aldon fairly soon.
If you delay, it will be a 2 step upgrade to version 8.3 (coming later this
year) and ensuing versions.
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Stone, Joel
Sent: Tuesday, March 08, 2016 3:28 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Aldon Lifecycle Manager for System i: can
thisproductsupportre-compilation WITHOUT checking out and promoting source?
True, but folks here didn't like the confusion that may bring one day when
trying to figure out a problem and having a home-grown command with the same
name as IBM's command.
At first we decided to rename the home-grown command to something like
RUNSQL2 and change each source member. But then I discovered that a simple
recompile will change the parm name and all is OK.
Also it seems like a good idea to retire the home-grown command completely
and immediately migrate to the IBM RUNSQL command entirely.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul
Nelson
Sent: Tuesday, March 08, 2016 2:51 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: Aldon Lifecycle Manager for System i: can this
productsupportre-compilation WITHOUT checking out and promoting source?
You could save yourself some headaches by having your home-grown RUNSQL
statement in a library other than QSYS, and modify QSYSLIBL to have QSYS as
the second library in the list.
You will then have the ability to modify (and test) your code at your
leisure before taking away the home grown command altogether.
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Stone, Joel
Sent: Tuesday, March 08, 2016 2:09 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Aldon Lifecycle Manager for System i: can this
productsupportre-compilation WITHOUT checking out and promoting source?
Thanks for your post.
Going from 5.4 to 7.1.
CACMS Rel 07.5G Aldon Lifecycle Manager for System i
Need to recompile because we had a home-grown version of RUNSQL which had a
parm name of "STMT" for the SQL command. The new 7.1 IBM RUNSQL command
uses the parm name "SQL" to hold the SQL commands.
When we used our homegrown RUNSQL command, we never explicitly named the
parm but rather used positioning; so each use is coded something like RUNSQL
'UPDATE CustFile set FlagFile = ''N'''
I have found that if I simply recompile any CL containing the RUNSQL
statement, it will then function properly with the IBM RUNSQL command
instead of the home grown version.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Charles Wilt
Sent: Tuesday, March 08, 2016 1:37 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Aldon Lifecycle Manager for System i: can this product
supportre-compilation WITHOUT checking out and promoting source?
Why do you think you need to recompile programs due to an OS upgrade?
Charles
On Tue, Mar 8, 2016 at 2:18 PM, Paul Nelson <nelsonp@xxxxxxxxxxxxx> wrote:
What is your current OS level? Do you have multiple machines? I'm not sure
why you would recompile on the new target platform, but if you do, you
will
lose the object control level identifiers that Aldon places on each object
it creates and deploys.
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Stone, Joel
Sent: Tuesday, March 08, 2016 1:08 PM
To: Midrange Systems Technical Discussion
Subject: Aldon Lifecycle Manager for System i: can this product
supportre-compilation WITHOUT checking out and promoting source?
We are upgrading our OS to 7.1.
I would prefer not to check out source members if they don't need to be
altered.
Can Aldon's Lifecycle Manager for System I handle recompiling source on
the
new target platform without checking out the source?
Any idea how to accomplish?
Thanks in advance.
______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs
Skyscan service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
midrange.com
