HLQ change of SMP/E files

Discussion:

(too old to reply)

Sankaranarayanan, Vignesh

2018-05-01 12:43:38 UTC

Hello All,

A scenario for your consideration...

Let's assume I have SMPE.* as the usual location for my SMP/E files (CSI, SMP*, DIST and TARG files).
There is now a product installed elsewhere... at WHYNOT.*

If I am to move everything from WHYNOT.* to SMPE.*, will DDDEFs be the only thing to fully list out and modify?
Both the HLQs just go to different VOLSER, i.e., they're not SMS managed.

Thoughts... ? Is this possible, is this worth trying?

- Vignesh
Mainframe Infrastructure

MARKSANDSPENCER.COM
________________________________
Unless otherwise stated above:
Marks and Spencer plc
Registered Office:
Waterside House
35 North Wharf Road
London
W2 1NW

Registered No. 214436 in England and Wales.

Telephone (020) 7935 4422
Facsimile (020) 7487 2670

www.marksandspencer.com

Please note that electronic mail may be monitored.

This e-mail is confidential. If you received it by mistake, please let us know and then delete it from your system; you should not copy, disclose, or distribute its contents to anyone nor act in reliance on this e-mail, as this is prohibited and may be unlawful.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

John McKown

2018-05-01 13:14:38 UTC

Permalink

On Tue, May 1, 2018 at 7:44 AM, Sankaranarayanan, Vignesh <

Post by Sankaranarayanan, Vignesh
Hello All,
A scenario for your consideration...
Let's assume I have SMPE.* as the usual location for my SMP/E files (CSI,
SMP*, DIST and TARG files).
There is now a product installed elsewhere... at WHYNOT.*
If I am to move everything from WHYNOT.* to SMPE.*, will DDDEFs be the
only thing to fully list out and modify?
Both the HLQs just go to different VOLSER, i.e., they're not SMS managed.
Thoughts... ? Is this possible, is this worth trying?

I'm a bit light headed today due to a medical procedure yesterday. But if
my brain is not lying to me, you want to do a "mass rename" of the DDDEFs
in SMP/E. If so, then look at the SMP/E ZONEEDIT command.

SET BOUNDRY(...)
ZONEEDIT DDDEF
CHANGE DATASET(WHYNOT.*,SMPE.*)
ENDZONEDIT

ref:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.gim1000/chpzed.htm
(start of doc)
ref:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.gim1000/zedex2.htm
(example)

Post by Sankaranarayanan, Vignesh
- Vignesh
Mainframe Infrastructure
MARKSANDSPENCER.COM

--
We all have skeletons in our closet.
Mine are so old, they have osteoporosis.

Maranatha! <><
John McKown

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

CM Poncelet

2018-05-02 02:59:03 UTC

Permalink

Yes, and there is more to it than that.

ZONEEXPORT, UCLIN, ZONEDELETE, DEL/ADD/REP ZONEINDEX GZONE/DZONE/TZONE,
ENDUCL, ZONEIMPORT ... RELATED(<whatever zone>) etc. and then
DEL/REP/ADD DDDEF(<whatever>) DA(<WHYNOT.whatever else>) SHR to point at
the DDDEF 'WHYNOT' DSNs in the GZONE/DZONE/TZONE.

Chris Poncelet (retired sysprog)

There are always other things to be mindful of. Think of other places the HLQ WHYNOT could appear.
Do any of the SYSMODs for this product contain ++JCLIN statements? Did the vendor supply any JCLIN commands?
Do any of the product elements that contain text, such as MAC, SRC, or DATA, contain dataset names (some products include sample JCL procedures)?

-----Original Message-----
Of Sankaranarayanan, Vignesh
Sent: Tuesday, May 01, 2018 6:53 AM
Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files
Thanks John. Hope you're doing alright.
So will a ZONEEDIT be all, or are there other things to be mindful of?
– Vignesh
Mainframe Infrastructure
-----Original Message-----
Behalf Of John McKown
Sent: Tuesday 01-May-2018 18:46
Subject: [EXTERNAL] Re: HLQ change of SMP/E files
On Tue, May 1, 2018 at 7:44 AM, Sankaranarayanan, Vignesh <

Post by Sankaranarayanan, Vignesh
Hello All,
A scenario for your consideration...
Let's assume I have SMPE.* as the usual location for my SMP/E files
(CSI, SMP*, DIST and TARG files).
There is now a product installed elsewhere... at WHYNOT.*
If I am to move everything from WHYNOT.* to SMPE.*, will DDDEFs be the
only thing to fully list out and modify?
Both the HLQs just go to different VOLSER, i.e., they're not SMS managed.
Thoughts... ? Is this possible, is this worth trying?

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
.

Kurt Quackenbush

2018-05-02 12:31:41 UTC

Permalink

So will a ZONEEDIT be all, or are there other things to be mindful of?

Sankaranarayanan, Vignesh

2018-05-02 17:26:26 UTC

Permalink

Hi Kurt,

Thanks for this; the product is in its own target and dlip zones, product has its own CSI.
So the ZONEINDEX is for consideration only when TGT and DLIB have their own zones, or even if they're all in a single product CSI?

PS: Big fan of getting replies from various IBM development teams!!

– Vignesh
Mainframe Infrastructure

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Kurt Quackenbush
Sent: Wednesday 02-May-2018 18:03
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files

So will a ZONEEDIT be all, or are there other things to be mindful of?

ZONEEDIT is all you need to update the data set names in the DDDEF entries for the target and dlib data sets. However, is this product installed in its own target and dlib zones? Are those zones in their own CSI data sets? If you'll be renaming the CSI data sets too, then you'll need to update the ZONEINDEX subentries in the global zone, like
this:

SET BDY(GLOBAL).
UCLIN.
DEL GZONE ZONEINDEX((tgtzonename)).
ADD GZONE ZONEINDEX((tgtzonename,WHYNOT.dataset.name.CSI,TARGET)).
DEL GZONE ZONEINDEX((dlibzonename)).
ADD GZONE ZONEINDEX((dlibzonename,WHYNOT.dataset.name.CSI,DLIB)).
ENDUCL.

Kurt Quackenbush -- IBM, SMP/E Development

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

MARKSANDSPENCER.COM
________________________________
Unless otherwise stated above:
Marks and Spencer plc
Registered Office:
Waterside House
35 North Wharf Road
London
W2 1NW

Registered No. 214436 in England and Wales.

Telephone (020) 7935 4422
Facsimile (020) 7487 2670

www.marksandspencer.com

Please note that electronic mail may be monitored.

This e-mail is confidential. If you received it by mistake, please let us know and then delete it from your system; you should not copy, disclose, or distribute its contents to anyone nor act in reliance on this e-mail, as this is prohibited and may be unlawful.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

CM Poncelet

2018-05-03 03:33:00 UTC

Permalink

There is more to it than that if you are cloning (copying) a CSI into
another CSI. E.g.

"ZONEEXPORT, UCLIN, ZONEDELETE, DEL/ADD/REP ZONEINDEX GZONE/DZONE/TZONE,"
"ENDUCL, ZONEIMPORT ... RELATED(<whatever zone>) etc. and then"
"DEL/REP/ADD DDDEF(<whatever>) DA(<WHYNOT.whatever else>) SHR to point at"
"the DDDEF 'WHYNOT' DSNs in the GZONE/DZONE/TZONE."

You need also to relate your cloned DZONE and TZONE to each other in the
cloned CSI, as in e.g.

SET BOUNDARY(DZONE)
.
ZONEIMPORT (DZONE) INFILE(IMPORTDZ) INTO(DZONE) RELATED(TZONE)
.
SET BOUNDARY(TZONE)
.
ZONEIMPORT (TZONE) INFILE(IMPORTTZ) INTO(TZONE) RELATED(DZONE)
.

All the original CSI's SMP/E datasets should be IEBCOPY'd or IEBGENER'd
to 'WHYNOT.*' datasets - and the cloned CSI's DDDEFs then updated to
point at the 'WHYNOT.*' datasets in its GLOBAL, DZONE and TZONE.
(Otherwise any RECEIVE, APPLY and ACCEPTs would be applied to the
original CSI's SMP/E datasets.)

Chris Poncelet (retired sysprog)

Post by Sankaranarayanan, Vignesh
Hi Kurt,
Thanks for this; the product is in its own target and dlip zones, product has its own CSI.
So the ZONEINDEX is for consideration only when TGT and DLIB have their own zones, or even if they're all in a single product CSI?
PS: Big fan of getting replies from various IBM development teams!!
– Vignesh
Mainframe Infrastructure
-----Original Message-----
Sent: Wednesday 02-May-2018 18:03
Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files

So will a ZONEEDIT be all, or are there other things to be mindful of?

ZONEEDIT is all you need to update the data set names in the DDDEF entries for the target and dlib data sets. However, is this product installed in its own target and dlib zones? Are those zones in their own CSI data sets? If you'll be renaming the CSI data sets too, then you'll need to update the ZONEINDEX subentries in the global zone, like
SET BDY(GLOBAL).
UCLIN.
DEL GZONE ZONEINDEX((tgtzonename)).
ADD GZONE ZONEINDEX((tgtzonename,WHYNOT.dataset.name.CSI,TARGET)).
DEL GZONE ZONEINDEX((dlibzonename)).
ADD GZONE ZONEINDEX((dlibzonename,WHYNOT.dataset.name.CSI,DLIB)).
ENDUCL.
Kurt Quackenbush -- IBM, SMP/E Development
----------------------------------------------------------------------
MARKSANDSPENCER.COM
________________________________
Marks and Spencer plc
Waterside House
35 North Wharf Road
London
W2 1NW
Registered No. 214436 in England and Wales.
Telephone (020) 7935 4422
Facsimile (020) 7487 2670
www.marksandspencer.com
Please note that electronic mail may be monitored.
This e-mail is confidential. If you received it by mistake, please let us know and then delete it from your system; you should not copy, disclose, or distribute its contents to anyone nor act in reliance on this e-mail, as this is prohibited and may be unlawful.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

Sankaranarayanan, Vignesh

2018-05-03 04:16:14 UTC

Permalink

Hi Chris,

Is it not possible to move the existing datasets into their new names (rename), and do the required UCL work.

– Vignesh
Mainframe Infrastructure

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of CM Poncelet
Sent: Thursday 03-May-2018 09:06
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files

There is more to it than that if you are cloning (copying) a CSI into another CSI. E.g.

"ZONEEXPORT, UCLIN, ZONEDELETE, DEL/ADD/REP ZONEINDEX GZONE/DZONE/TZONE,"
"ENDUCL, ZONEIMPORT ... RELATED(<whatever zone>) etc. and then"
"DEL/REP/ADD DDDEF(<whatever>) DA(<WHYNOT.whatever else>) SHR to point at"
"the DDDEF 'WHYNOT' DSNs in the GZONE/DZONE/TZONE."

You need also to relate your cloned DZONE and TZONE to each other in the cloned CSI, as in e.g.

SET BOUNDARY(DZONE)
.
ZONEIMPORT (DZONE) INFILE(IMPORTDZ) INTO(DZONE) RELATED(TZONE) .
SET BOUNDARY(TZONE)
.
ZONEIMPORT (TZONE) INFILE(IMPORTTZ) INTO(TZONE) RELATED(DZONE) .

All the original CSI's SMP/E datasets should be IEBCOPY'd or IEBGENER'd to 'WHYNOT.*' datasets - and the cloned CSI's DDDEFs then updated to point at the 'WHYNOT.*' datasets in its GLOBAL, DZONE and TZONE.
(Otherwise any RECEIVE, APPLY and ACCEPTs would be applied to the original CSI's SMP/E datasets.)

Chris Poncelet (retired sysprog)

Post by Sankaranarayanan, Vignesh
Hi Kurt,
Thanks for this; the product is in its own target and dlip zones, product has its own CSI.
So the ZONEINDEX is for consideration only when TGT and DLIB have their own zones, or even if they're all in a single product CSI?
PS: Big fan of getting replies from various IBM development teams!!
– Vignesh
Mainframe Infrastructure
-----Original Message-----
On Behalf Of Kurt Quackenbush
Sent: Wednesday 02-May-2018 18:03
Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files

So will a ZONEEDIT be all, or are there other things to be mindful of?

ZONEEDIT is all you need to update the data set names in the DDDEF
entries for the target and dlib data sets. However, is this product
installed in its own target and dlib zones? Are those zones in their
own CSI data sets? If you'll be renaming the CSI data sets too, then
you'll need to update the ZONEINDEX subentries in the global zone, like
SET BDY(GLOBAL).
UCLIN.
DEL GZONE ZONEINDEX((tgtzonename)).
ADD GZONE ZONEINDEX((tgtzonename,WHYNOT.dataset.name.CSI,TARGET)).
DEL GZONE ZONEINDEX((dlibzonename)).
ADD GZONE ZONEINDEX((dlibzonename,WHYNOT.dataset.name.CSI,DLIB)).
ENDUCL.
Kurt Quackenbush -- IBM, SMP/E Development
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
MARKSANDSPENCER.COM
________________________________
Marks and Spencer plc
Waterside House
35 North Wharf Road
London
W2 1NW
Registered No. 214436 in England and Wales.
Telephone (020) 7935 4422
Facsimile (020) 7487 2670
www.marksandspencer.com
Please note that electronic mail may be monitored.
This e-mail is confidential. If you received it by mistake, please let us know and then delete it from your system; you should not copy, disclose, or distribute its contents to anyone nor act in reliance on this e-mail, as this is prohibited and may be unlawful.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

Kurt Quackenbush

2018-05-03 12:57:48 UTC

Permalink

Post by Sankaranarayanan, Vignesh
Thanks for this; the product is in its own target and dlip zones,
product has its own CSI. So the ZONEINDEX is for consideration only
when TGT and DLIB have their own zones, or even if they're all in a
single product CSI?

Each target and dlib zone has its own ZONEINDEX, and each ZONEINDEX
points to the CSI data set that contains that zone. Therefore, if you
change the name of the CSI data set that contains a particular zone,
then you need to update the ZONEINDEX for that zone.

Kurt Quackenbush -- IBM, SMP/E Development

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

Kurt Quackenbush

2018-05-02 12:44:52 UTC

Permalink

Ooh... almost forgot the other question - is there a way to test run
this, equivalent of ADRDSSU's TYPRUN=NORUN?

Carmen Vitullo

2018-05-02 12:53:01 UTC

Permalink

In a case like this I'd like to use the fixcat's like FIXCAT(IBM.Coexistence.z/OS.V2R1 FIXCAT + (IBM.Coexistence.z/OS.V2R2) that are available now, it may produce a lot of required PTF's but SHOPZ + fixcats for required service for 2.1 and 2.2 ?
or choose the upgrade option in the PSP buckets ?

Carmen Vitullo

----- Original Message -----

From: "Kurt Quackenbush" <***@US.IBM.COM>
To: IBM-***@LISTSERV.UA.EDU
Sent: Wednesday, May 2, 2018 7:41:07 AM
Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files

Ooh... almost forgot the other question - is there a way to test run
this, equivalent of ADRDSSU's TYPRUN=NORUN?

No, no CHECK operand on ZONEEDIT. Frankly its a pretty safe operation,
but if you're concerned then make a copy of your CSI data set(s) that
contain the target and dlib zones and try it out on the copy first.

Kurt Quackenbush -- IBM, SMP/E Development

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

Carmen Vitullo

2018-05-02 13:04:58 UTC

Permalink

feels like a friday :( sorry I intended to respond to this POST
: z/OS 1.13 maintenance concern. May 2, 2018 7:56 AM

Carmen Vitullo

----- Original Message -----

From: "Carmen Vitullo" <***@HUGHES.NET>
To: IBM-***@LISTSERV.UA.EDU
Sent: Wednesday, May 2, 2018 7:54:01 AM
Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files

In a case like this I'd like to use the fixcat's like FIXCAT(IBM.Coexistence.z/OS.V2R1 FIXCAT + (IBM.Coexistence.z/OS.V2R2) that are available now, it may produce a lot of required PTF's but SHOPZ + fixcats for required service for 2.1 and 2.2 ?
or choose the upgrade option in the PSP buckets ?

Carmen Vitullo

----- Original Message -----

From: "Kurt Quackenbush" <***@US.IBM.COM>
To: IBM-***@LISTSERV.UA.EDU
Sent: Wednesday, May 2, 2018 7:41:07 AM
Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files

Ooh... almost forgot the other question - is there a way to test run
this, equivalent of ADRDSSU's TYPRUN=NORUN?

Paul Gilmartin

2018-05-01 15:25:33 UTC

Permalink

Post by Sankaranarayanan, Vignesh
Let's assume I have SMPE.* as the usual location for my SMP/E files (CSI, SMP*, DIST and TARG files).
There is now a product installed elsewhere... at WHYNOT.*
If I am to move everything from WHYNOT.* to SMPE.*, will DDDEFs be the only thing to fully list out and modify?
Both the HLQs just go to different VOLSER, i.e., they're not SMS managed.
Thoughts... ? Is this possible, is this worth trying?

Ih the past, for a new installation, I have relied on tailoring the JCL, both DD statements
and SMPCNTL, that creates the CSI.

Nowadays, "DD *,SYMBOLS=..." could facilitate this.

-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN