In
<[EMAIL PROTECTED]>,
on 11/30/2006
at 08:33 AM, "Chase, John" <[EMAIL PROTECTED]> said:
>If you have two or more "IPL volumes" for a given z/OS image, the
>implication is that you also have two or more instances of
>SYS1.PARMLIB which you must keep synchronized to avoid astonishment
>when IP
On Thu, 30 Nov 2006 16:40:05 -0500, Horein, Steve (HAR-ORL) wrote:
>Well !
>So basically I'm not in a very good position, and back to square one. It
>seems to me that to accomplish what I want, and maintain Production
>integrity, I need to create an uncataloged copy of .IODFxx (which
>is found in
---
Horein, Steve (HAR-ORL) wrote:
Well !
So basically I'm not in a very good position, and back to square one. It
seems to me that to accomplish what I want, and maintain Production
integrity, I need to create an uncataloged copy
Sys1.parmlib should be empty anyway. It's fine on ipl volume.
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Marchant
> Sent: Thursday, November 30, 2006 6:14 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: Mo
ittle bit of pain to prove 15 year old theory to satisfy the auditors,
and to get to a more modern structure, I have to do it!
Steve Horein
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Choate, Bill
Sent: Thursday, November 30, 2006 5:01 PM
ubject: Re: Moving LOADxx
Well !
So basically I'm not in a very good position, and back to square one. It
seems to me that to accomplish what I want, and maintain Production
integrity, I need to create an uncataloged copy of .IODFxx (which
is found in HSA) on a new volume. I then create SYSx.
Well !
So basically I'm not in a very good position, and back to square one. It
seems to me that to accomplish what I want, and maintain Production
integrity, I need to create an uncataloged copy of .IODFxx (which
is found in HSA) on a new volume. I then create SYSx.IPLPARM on this new
IODF volume
On Thu, 30 Nov 2006 11:51:20 -0600, Matthew Stitt <[EMAIL PROTECTED]> wrote:
>I find it to my advantage to keep SYS1.PARMLIB on the IPL volume. I catalog
>it with VOLSER of ** so I can find it on whichever volume I IPL from.
>
>I also don't change or put anything into it that IBM did not prov
I find it to my advantage to keep SYS1.PARMLIB on the IPL volume. I catalog
it with VOLSER of ** so I can find it on whichever volume I IPL from.
I also don't change or put anything into it that IBM did not provide when
the system was installed. Since I have multiple systems, each system has
Tom Marchant wrote:
On Wed, 29 Nov 2006 15:16:12 -0800, Jerry Whitteridge
<[EMAIL PROTECTED]> wrote:
Why not just use something like LOADPx for the production LOADxx and
LOADSx for the sandbox ?
You can't do that. The xx in LOADxx is a hexadecimal value: 00-FF.
You're confusing
On Thu, 30 Nov 2006 07:29:01 -0600, Tom Marchant <[EMAIL PROTECTED]>
wrote:
>On Wed, 29 Nov 2006 15:16:12 -0800, Jerry Whitteridge
><[EMAIL PROTECTED]> wrote:
>
>>Why not just use something like LOADPx for the production LOADxx and
>>LOADSx for the sandbox ?
>
>You can't do that. The xx in LOADxx
Chase, John wrote:
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of R.S.
Tom Marchant wrote:
On Thu, 30 Nov 2006 15:05:27 +0100, R.S. wrote:
Tom Marchant wrote:
[...]
I _strongly_ suggest that you move SYS1.PARMLIB off the IPL
volume.
Why ???
So that you don't h
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of R.S.
>
> Tom Marchant wrote:
> > On Thu, 30 Nov 2006 15:05:27 +0100, R.S. wrote:
> >
> >> Tom Marchant wrote:
> >> [...]
> >>> I _strongly_ suggest that you move SYS1.PARMLIB off the IPL
volume.
> >> Why ???
> >
> >
Tom Marchant wrote:
On Thu, 30 Nov 2006 15:05:27 +0100, R.S. wrote:
Tom Marchant wrote:
[...]
I _strongly_ suggest that you move SYS1.PARMLIB off the IPL volume.
Why ???
So that you don't have to be concerned about keeping myltiple copies
of SYS1.PARMLIB in sync.
OK, however keeping *sin
On Thu, 30 Nov 2006 15:05:27 +0100, R.S. wrote:
>Tom Marchant wrote:
>[...]
>> I _strongly_ suggest that you move SYS1.PARMLIB off the IPL volume.
>
>Why ???
>
So that you don't have to be concerned about keeping myltiple copies
of SYS1.PARMLIB in sync.
--
Tom Marchant
On Thu, 30 Nov 2006 15:00:41 +0100, R.S. wrote:
>Tom Marchant wrote:
>>
>> The xx in LOADxx is a hexadecimal value: 00-FF.
>
>The above is not true. You can use alphanumerical characters. I'm pretty
>sure, because I use "non-hex" characters.
>
sorry about that. Of course you are correct. I wa
Tom Marchant wrote:
[...]
I _strongly_ suggest that you move SYS1.PARMLIB off the IPL volume.
Why ???
--
Radoslaw Skorupka
Lodz, Poland
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL P
Tom Marchant wrote:
On Wed, 29 Nov 2006 15:16:12 -0800, Jerry Whitteridge
<[EMAIL PROTECTED]> wrote:
Why not just use something like LOADPx for the production LOADxx and
LOADSx for the sandbox ?
You can't do that. The xx in LOADxx is a hexadecimal value: 00-FF.
The above is not true. You
remove the
SYS1.PARMLIB from the IODF volume.
Bill Choate
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of
Horein, Steve (HAR-ORL)
Sent: Thursday, November 30, 2006 8:43 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Moving LOADxx
Oy!
So if LOADxx
On Wed, 29 Nov 2006 17:01:53 -0600, Steve Horein wrote:
>Maybe I have a new one for you all!
>I would like to move LOADxx out of SYS1.PARMLIB and into SYSx.IPLPARM on
the
>IODF volume. Really no big deal, just do it, right? Well, no. I have 2
>LPARS, Production and Sandbox. At this time, SYS1.PAR
@BAMA.UA.EDU
Subject: Re: Moving LOADxx
Once you create SYSx.IPLPARM on the IODF volume, SYS1.PARMLIB will
not be used. And BTW, the "x" in SYSx has to be 0-9.
--
Tom Marchant
--
For IBM-MAIN subscribe / signoff / arch
The xx is not limited to 00-FF. I have used values such z4, 2t, 2r without any
problems.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tom
Marchant
Sent: Thursday, November 30, 2006 8:29 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Moving
On Wed, 29 Nov 2006 17:18:10 -0600, Matthew Stitt <[EMAIL PROTECTED]>
wrote:
>You are making the issue more complicated than it should be.
>
>Go ahead an move the LOADxx parm member into SYSx.IPLPARM. For testing
>purposes you could change the XX to some other suffix and use that for the
>syste
, November 30, 2006 7:32 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Moving LOADxx
Also, LOADxx does not support system symbols other than &SYSR1 which is
supported in only one specific case. So you cannot use &SYSNAME in any
case.
Peter Relson
z/OS Core Technolog
On Wed, 29 Nov 2006 15:16:12 -0800, Jerry Whitteridge
<[EMAIL PROTECTED]> wrote:
>Why not just use something like LOADPx for the production LOADxx and
>LOADSx for the sandbox ?
You can't do that. The xx in LOADxx is a hexadecimal value: 00-FF.
--
Tom Marchant
Also, LOADxx does not support system symbols other than &SYSR1 which is
supported in only one specific case. So you cannot use &SYSNAME in any
case.
Peter Relson
z/OS Core Technology Design
--
For IBM-MAIN subscribe / signoff / a
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Matthew Stitt
Sent: Wednesday, November 29, 2006 6:18 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Moving LOADxx
You are making the issue more complicated than it should be.
Go ahead an move the LOADxx parm member into SY
You are making the issue more complicated than it should be.
Go ahead an move the LOADxx parm member into SYSx.IPLPARM. For testing
purposes you could change the XX to some other suffix and use that for the
system IPL. If you have a problem, you can change the LOAD parm back to the
original LOA
Why not just use something like LOADPx for the production LOADxx and
LOADSx for the sandbox ? Then you can copy your current LOADxx's into
those members and coexist. No change necessary to your IODF setup.
Otherwise use 2 different IODF HLQ's. You can copy an IODF and maintain
the token with no adv
Maybe I have a new one for you all!
I would like to move LOADxx out of SYS1.PARMLIB and into SYSx.IPLPARM on the
IODF volume. Really no big deal, just do it, right? Well, no. I have 2
LPARS, Production and Sandbox. At this time, SYS1.PARMLIB lives on the
Sysres for each system, and is directly cat
30 matches
Mail list logo
