If it is ACCEPTED, it is not in the Global zone, unless you left it there and did not allow a purge. The receive and install of a new CICS into/from the common global zone will mark the CICS FMID SUP'd. If you are using separate target and DLIB zones for new CICS, then you create a new one of each, install into it and new libraries, and when you no longer need the old CICS, simply remove the zone definitions from the global zone and delete the CSI's

Doug

.
Doug Fuerst
Principal Consultant
BK Associates
718.921.2620 (O)
917.572.7364 (C)
[email protected]



------ Original Message ------
From: "venkat kulkarni" <[email protected]>
To: [email protected]
Sent: 07-Jul-15 9:41:49 AM
Subject: Re: Product Remove from z/OS

Hello All,
Thanks for suggestions.We are using common global CSI for all CICS version and having diff target and distribution zone and related CSI
for different CSI version .

As I mentioned earlier, that all FMID related to this this version of CICS are in accept state . So, how can I use reject command to
delete that FMID from SMPE.

              Can you please advise me .

Regards
Venkat

On Tue, Jul 7, 2015 at 5:03 PM, John Eells <[email protected]> wrote:

 [email protected] (venkat kulkarni) wrote:

 Hello Group,
We have requirement to remove older version of CICS
 from
our z/OS system but in SMPE all FMID related to that particular version
 of
 CICS is in accepted state.

As I have to remove this product from system , I will remove all target
 and
 distribution libraries and region specific datasets.

but I am not sure how to remove this SMPE related stuff of this CICS from
 z/OS system as it is in accepted state.

 Any pointer will be helpful.

 <snip>

If the CICS CSIs are unique to that level of CICS, just delete the CSI data sets. If the CICS CSIs are shared among multiple levels of CICS, you can use the ZONEDELETE command, and then REJECT the PTFs for the CICS FMIDs that are unique to the release and remove the FMIDs from the global zone.

 Before doing anything at all, though, consider renaming the target
libraries using an HLQ with UACC(NONE) to which nobody else has access, and waiting for an IPL. If there's no fallout, you can be pretty sure they're not in use after that...and if they are in use, you can recover quickly if you must, and you'll know who was using them so you can fix that and try
 again.

 HTH,

 --
 John Eells
 z/OS Technical Marketing
 IBM Poughkeepsie
 [email protected]

----------------------------------------------------------------------
 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



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to