Thanks Jon,
Our systems are in sysplex with different version of z/OS
(in my case its z/OS 1.13 and z/OS 2.1 ) systems. Currently I am in the
process of installing CICS 5.2 release and we have multiple CICS version in
our shop also global CSI is common for all CICS version present in systems.
The error, I mentioned before was getting during receiving MCS and HOLD
data for CICS 5.2 using CBPDO order.
Just to cross check, I also run receive latest FIXCAT hold data job and
encountered same issues.
So, now my queries are
1) Why is it necessary to run UPGRADE parameter in issue.
2) Even if I run receive Job from z/OS 2.1 with setting boundary of GLobal
zone which is part of common global csi
//SMPCNTL DD *
SET BDY (GLOBAL) .
UPGRADE.
RECEIVE HOLDDATA .
then I will not be able to use this CICS global CSI from my z/OS 1.13
systems. So, another alternative is to run this Job from z/OS 1.13 system
and then we can use in z/OS 2.1 also.
3) After receive, do we have to specify UPGRADE option while doing apply
and accept as well or it is only required for receive.
On Wed, Aug 13, 2014 at 11:07 PM, Jon Perryman <[email protected]> wrote:
> Never permanently add UPGRADE to your JCL. You always want to make the
> decision to upgrade a zone becase it PERMANENTLY upgrades that zone. I'll
> discuss this in terms of z/OS release but it actually tied to the SMP/e
> release/PTF level (not z/OS). Let's say are running 1.12, 1.13 and 2.1 z/OS
> and you want SMP/e to run on all 3 of those versions if possible. If you
> run the UPGRADE from 2.1, then this zone cannot be updated from 1.12 or
> 1.13. If you did the UPGRADE from 1.13, then you can't run SMP/e against
> this zone on your 1.12 system but can run it on 1.13 & 2.1.
>
> WARNING: Run UPGRADE from the lowest level system because you can't back
> it out after the change. If the receive holddata still fails, then try it
> on the next higher release but remember you can't use SMP/e from that
> system.
>
> WARNING: Permanently adding UPGRADE to your JCL could risk using SMP/e
> from older systems. You could accidentally running the job on your newly
> installed 2.1 system.
>
> Jon Perryman
>
>
>
> On Wednesday, August 13, 2014 9:35 AM, Mainframe Mainframe <
> [email protected]> wrote:
>
>
> >
> >Thanks for reply. I am basically receiving HOLD data and getting this
> >issue. So, as mentioned in last update, Do I have to just update receive
> >JCL with
> >
> >//SMPCNTL DD *
> > SET BDY (GLOBAL) .
> > UPGRADE.
> > RECEIVE HOLDDATA .
> >
> >above UPGRADE option and it will receive the data.But I am still not clear
> >
>
> ----------------------------------------------------------------------
> 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
