Hello All,
Thanks for suggestion. We coded something like below for
removing those FMID from both target and distribution zone of CICS .
//FMIDDEL JOB ,,CLASS=A,MSGCLASS=A,REGION=0M,NOTIFY=&SYSUID
//S1 EXEC PGM=GIMSMP,
// PARM='PROCESS=WAIT',
// DYNAMNBR=120
//SMPCSI DD DISP=SHR,DSN='SMPE.CICS.GLOBAL.CSI'
//SMPHOLD DD DUMMY
//SMPLOG DD SYSOUT=*
//SMPOUT DD SYSOUT=*
//SMPRPT DD SYSOUT=*
//SMPLIST DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SMPPTFIN DD *
++FUNCTION (MSZ0001) REWORK(2015100)
/***********************************************************/
/* DELETE HCI6400 FROM ALL ZONES */
/***********************************************************/
.
++VER (Z038)
DELETE(HCI6400) .
/*
//SMPCNTL DD *
SET BOUNDARY (GLOBAL).
RECEIVE SELECT (MSZ0001) SYSMOD.
SET BOUNDARY (CICS31T) .
APPLY SELECT (MSZ0001) .
SET BOUNDARY (CICS31D) .
ACCEPT SELECT (MSZ0001) .
SET BOUNDARY(CICS31T) .
UCLIN.
DEL SYSMOD(MSZ0001).
DEL SYSMOD(HCI6400).
ENDUCL.
SET BOUNDARY(CICS31D) .
UCLIN.
DEL SYSMOD(MSZ0001).
DEL SYSMOD(HCI6400).
ENDUCL.
SET BOUNDARY (GLOBAL).
REJECT APARS FUNCTIONS PTFS USERMODS FORFMID(HCI6400).
RESETRC.
UCLIN.
DEL GLOBALZONE FMID(MSZ0001).
DEL GLOBALZONE FMID(HCI6400).
ENDUCL.
/*
Please correct, If I made any mistake in this or Am I following wrong path.
On Thu, Jul 9, 2015 at 9:21 AM, Anthony Thompson <[email protected]
> wrote:
> All that UCLIN does is get rid of the GLOBAL zone pointers to the
> Tzone/Dzone's. It does nothing to the tzone/dzone themselves or to the
> (presumably separate) VSAM clusters that contain those Tzone/Dzone's. You
> can delete the VSAM clusters either before or after, it doesn't matter,
> since the UCLIN only touches the global zone.
>
> Before doing that, have you applied/ accepted all maintenance for the
> version of CICS you're trying to get rid of? So there's nothing relevant
> left in the SMPPTS, SCDS, MTS, LTS, STS?
>
> In any event, simply deleting the tzone/dzone doesn't lose all information
> about the CICS you're trying to get rid of. The Global zone will still have
> product and feature entries.
>
> You've already been told how to do it, by Craig Pace. Code a usermod with
> ++DELETE MCS for the CICS fmid's and receive/apply/accept that usermod
> (yes, accept a usermod! This is about the only situation I would do so).
>
> Lastly, why do you have a global zone for all versions of CICS? When I
> install the next version of CICS, I create an entirely new SMP/E
> environment, with its own global zone. I don't see any advantage to your
> approach.
>
> Ant.
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Mainframe Mainframe
> Sent: Thursday, 9 July 2015 11:49 AM
> To: [email protected]
> Subject: Re: Product Remove from z/OS
>
> Hello,
> Thanks for suggestion.
>
> 1) We already have new version of CICS running under same global zone
> along with older CICS version still running.
> 2) My idea is to remove older CICS version from my z/OS systems.
> 3) We already have weekly back, So we are good in this case.
> 4) cics-fmids was not actual FMID, that was just for reference, I used in
> email.
> 5) As per your suggestion, I understood that , If I use
>
> SET BDY(GLOBAL).
> UCLIN.
> DEL DZONE(CIC31D) .
> ENDUCL.
>
> and same with target
>
> SET BDY(GLOBAL).
> UCLIN.
> DEL DZONE(CIC31T) .
> ENDUCL.
>
> Doing this will remove all entries from my global zone and later I can
> delete target and distribution CSI attached to these two CIC32T and
> CIC31D. Or do I have to delete these CSI dataset first using IDCAMS and
> then use above operand to delete both of these zones.
>
>
> Please suggest.
>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
