Hi Mate, yes, when Applied compatible fixes, I had re-applied One of userexist for TSO as well.
Hope you got my error screenshot in previous email, thing is its failing only with TSO SUMMIT command coded internally, But at this moment I'm unable bypass this. Thanks On Tue, Nov 20, 2018 at 8:15 PM Carmen Vitullo <[email protected]> wrote: > I upgraded ACF2 back in preporeation for Y2K and as I recall, when I > installed toleration I had to restore and reapply my usermods, some of > those usermods dealt with TSO submit exit processing and CICS signon > processing, did you have to reject/restore any usermods and if so did you > reapply ? > > > > Carmen Vitullo > > ----- Original Message ----- > > From: "Shashi Kumar" <[email protected]> > To: [email protected] > Sent: Tuesday, November 20, 2018 7:41:25 AM > Subject: z/OS 2.3 Migration Story > > Hello Mates, > > I'm unable to figure out root cause of the below issues after z/OS 2.3 > Migration, as Described below > > 1. Once we migrated from z/OS 2.3 (With CA ACF2 V16 security product), One > of the batch job got failed due to security issue with batch ID, where as > a batch code with TSO SUMMIT command within the batch job, and it failed > with very first instance after migration, How ever I had reached security > team to provide the required access, security team had code batch ID with > JCL attribute then it got completed successfully, but this batch was > successfully completing in z/OS 2.1 without JCL attribute, must wanted to > know does any new security rules come along with z/OS 2,3 (hoe ever I had > applied all CA z/OS 2.3 compatibility fixes as well), now current problem > is If I move onto production Lpar to migrate, what if all batch ID's > fail's > (Which has TSO summit command coded on it), it will be a disaster, can > some > tell me, these issue had reported in your system and what action you have > taken to mitigate this issue > > Hence I need your suggestion to mitigate this issue before the next > migration. > > 2. the batch ID had problem with another batch job, where as it was trying > to write to master catalogue (however I had try to create a new master > catalogue during migration unfortunately it didn't work out), where as > Batch ID previous used to write user catalogue but after migration it > tried > to write on master catalogue directly, and previously it didn't had write > access, only it had read access to master catalogue. > > Need your suggestion find out the root cause of this issue as well. > > Thanks and regards, > Shashi > > ---------------------------------------------------------------------- > 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
