Thanks. This worked for me on z/OS 1.13 system. Now moving forward, I want
to run FIXCAT for IBM.PRODUCTINSTALL-REQUIREDSERVICE
before starting CICS installation and to know the missing PTF in system.
But the issue is
//FIXCAT1 JOB (3623),'SAURABH',MSGCLASS=X,CLASS=A,
// NOTIFY=&SYSUID,REGION=0M
//SMPE EXEC PGM=GIMSMP
//SMPCSI DD DSN=SMPE.ZOS21.GLOBAL.CSI,DISP=SHR
//SMPHOLD DD *
//SMPOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SMPCNTL DD *
SET BDY (GLOBAL) .
REPORT MISSINGFIX ZONES(MVST100)
FIXCAT(IBM.PRODUCTINSTALL-REQUIREDSERVICE).
/*
If I specify CICS global CSI in SMPCSI DD name then what should I specify
in REPORT MISSINGFIX ZONES statement, as every CICS version will have it
own target zone . In our case we installing CICS 5.2 and corresponding
target zone doesnt exist till now.
Or we just have to run this missing fixcat report job with z/OS CSI and MVS
target zone.
On Thu, Aug 14, 2014 at 8:18 AM, Jon Perryman <[email protected]> wrote:
> Run UPGRADE on your 1.13 system. UPGRADE does not affect CICS. It only
> affects where you can run your SMP/e jobs for CICS.
>
> 1. I think your misunderstanding is with what this error message means.
> SMP/e as a product does NOT use compatibility PTF's. Instead, they require
> you use the UPGRADE command to set the zone's compatibility to the SMP/e
> release where the command is run. In your case, the error message says that
> HOLDDATA CATEGORY( ) is not compatible with the SMP/e release set in your
> global CSI. You need to set your SMP/e global zone to an SMP/e version that
> supports CATEGORY( ).
>
> 2. Yes, running upgrade on 1.13 will (probably) keep the zone compatible
> with 2.1 and 1.13. Running it from 2.1 will (maybe) make your global zone
> incompatible with 2.1. I say PROBABLY because UPGRADE is tied to the SMP/e
> PTF level (not z/OS PTF level).
>
> 3.I think CATEGORY( ) is a global zone parm but won't swear to it. Apply
> and accept probably won't see this parm. They may however have other parms
> that fail because they are not supported at the zones specified SMP/e PTF
> level. In that case, you may need to upgrade those zones.
>
> Jon Perryman
>
>
> On Wednesday, August 13, 2014 6:07 PM, Mainframe Mainframe <
> [email protected]> wrote:
>
>
> >
> >
> >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
> >
> >
> >
>
> ----------------------------------------------------------------------
> 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
