Re: CHGSYSVAL QSTRUPPGM VALUE parameter syntax

Brad,
That doesn't work for CHGSYSVAL.

On Thu, Aug 1, 2024 at 7:54 AM Brad Stone <bvstone@xxxxxxxxx> wrote:

Oh don't get me started on that... :)

My issue is when people ask how to use a specific command, especially one
with multiple entries for one parameter. If you want to know how to

format

it in a CL, just prompt it, enter the data you want and voila... perfect
formatting.

On Thu, Aug 1, 2024 at 6:50 AM Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx>
wrote:

That’s exactly what I thought of when I read that Patrik. Sometimes
folks just make things hard on themselves.

There are reasons to change the start up program programmatically but
those situations are normally with HA/DR environment swaps.




Jim Oberholtzer
Agile Technology Architects

On Aug 1, 2024, at 4:41 AM, Patrik Schindler <poc@xxxxxxxxxx> wrote:

Hello Dan,

Am 01.08.2024 um 03:38 schrieb Dan Bale <

dan.bale@xxxxxxxxxxxxxxxxxxxxx

:

IBM documentation appears to be severely lacking in describing the

proper format of the VALUE parameter string for the CHGSYSVAL QSTRUPPGM
command. The documentation I've seen has only a single space between

the

program name and the library name regardless of the length of the

program

name (e.g. 'QSTRUP QSYS'), but if memory serves from 20 years ago, I'm
pretty sure the program name starts in position 1 and the library name
starts in position 11.

Why not use wrksysval qstrup* and use 2=Change for a worry-free

screen

form?

:wq! PoC



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.