Re: SSI Corrupted Registers
On Sat, 30 Mar 2024 22:44:30 GMT "esst...@juno.com" wrote: :>I am looking at Sub System Interface Function Codes 04, 08, 10. and 50. : :>I Understand there's a protocol for providing response codes using SSOBRETN and Register 15 - :. :>What if upon entry to an SSI Function Routine Register 1 and Register 0 are corrupted or the respective eyecatcher's :>in the SSOB and/or SSCVT are not what is expected ? :>I don't think abending is acceptable as I suspect that would stop the scan of the SSCVT chain ? Correct ? : :>So what is the recommended action when Register 1 or Register 0 have been corrupted upon entry :> to a SSI Function Routine ? Assuming this is a true routine hung of the SSVT and not hooking SSI, to get to the subsystem requires that the SSIB points to your subsystem and the SSOB is a function you requested. I wouldn't even bother checking as it would require serious failures in MVS to get there. If hooking SSI, I would just pass it on. I remember code I saw that checked for MVS, and if not issued a WTO (SVC 35), which quite probably would cause other trouble to an OS that might not properly understand the SVC. -- Binyamin Dissen http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
SSI Corrupted Registers
. I am looking at Sub System Interface Function Codes 04, 08, 10. and 50. . I Understand there's a protocol for providing response codes using SSOBRETN and Register 15 - .. What if upon entry to an SSI Function Routine Register 1 and Register 0 are corrupted or the respective eyecatcher's in the SSOB and/or SSCVT are not what is expected ? I don't think abending is acceptable as I suspect that would stop the scan of the SSCVT chain ? Correct ? . So what is the recommended action when Register 1 or Register 0 have been corrupted upon entry to a SSI Function Routine ? . paul dange;o -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMP/E
Found the example that you provided. The execution that was performed was just the upgrade command by itself. Then the job was executed that performed the received and it failed. Then the job was executed as describe in the example as the first command then the receive command after the Upgrade command and that worked. I must have misunderstood how to use the UPGRADE command. Thanks for the assistance. Thank You -Original Message- From: IBM Mainframe Discussion List On Behalf Of Paul Feller Sent: Friday, March 29, 2024 7:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMP/E CAUTION! EXTERNAL SENDER! STOP, ASSESS, AND VERIFY Do you know this person? Were you expecting this email? If not, report it using the Report Phishing Button! I'll ask if you did the UPGRADE in the same run as the RECEIVE process. The example from the z/OS SMP/E Commands manual shows the UPGRADE command as part of the same run. The following is from the SMP/E command manual. SET BDY(ZOSTGT). UPGRADE. BYPASS(HOLDSYS) CHECK. In this example, the UPGRADE command indicates incompatible changes may be made to SMP/E data sets. If UPGRADE is not specified, then SMP/E stops any processing that would make incompatible changes to SMP/E data sets. In this example, the APPLY command would very likely fail if the UPGRADE command were not first run. However, once the UPGRADE command is run for a particular zone, then all SMP/E commands are authorized to make incompatible changes to all SMP/E data sets in that zone. Paul -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steely.Mark Sent: Friday, March 29, 2024 5:49 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMP/E I did perform the upgrade command on the global and target zone and nothing happen. The SMP/e level stayed the same and the receive still failed with the same error. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tom Marchant Sent: Friday, March 29, 2024 5:20 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMP/E CAUTION! EXTERNAL SENDER! STOP, ASSESS, AND VERIFY Do you know this person? Were you expecting this email? If not, report it using the Report Phishing Button! Just issue the UPGRADE command. IIRC FIXCAT support was added to SMP/E around 2008. Your global zone must have been created with a release of SMP/E before that. -- Tom Marchant On Fri, 29 Mar 2024 21:59:49 +, Steely.Mark wrote: >I recently received this message: GIM58903WSMP/E COULD NOT PROCESS A >++HOLD FIXCAT MCS BECAUSE IT WOULD HAVE MADE A CHANGE TO THE GLOBAL ZONE THAT > > CANNOT BE PROCESSED COMPLETELY BY PRIOR LEVELS OF SMP/E. USE THE > UPGRADE COMMAND TO ALLOW SMP/E TO MAKE > > SUCH CHANGES. > >The message says you can execute the upgrade command. ( I am not sure >if I can do that without having some type of maintenance applied) > >It has been a while since I upgraded SMP/e independently of a Service Pack or >some other type of installation. > >I thought I would just install the new release of SMP/e - for some reason I >can't find it on ShopzSeries. > >I have tried to look all over the internet for the answer, but I always gets >hits on installing other products using SMP/e. > >We are currently at SMP/E 37.13 >Our SMP/E is 2.4 FMID - HMP1K00. > >What should I do ? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMP/E
You might use the steplib as the one used to create the One, so it upgrades to same level. Which is level are you in? *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux and IBM I **| * *|* *Email**: i_mugz...@securiteam.co.il **|* *Mob**: +972 522 986404 **|* *Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il **|* בתאריך שבת, 30 במרץ 2024 ב-1:00 מאת Steely.Mark : > I recently received this message: GIM58903WSMP/E COULD NOT PROCESS A > ++HOLD FIXCAT MCS BECAUSE IT WOULD HAVE MADE A CHANGE TO THE GLOBAL ZONE > THAT > >CANNOT BE PROCESSED COMPLETELY BY PRIOR LEVELS OF SMP/E. USE THE > UPGRADE COMMAND TO ALLOW SMP/E TO MAKE > >SUCH CHANGES. > > The message says you can execute the upgrade command. ( I am not sure if > I can do that without having some type of maintenance applied) > > It has been a while since I upgraded SMP/e independently of a Service Pack > or some other type of installation. > > I thought I would just install the new release of SMP/e - for some reason > I can't find it on ShopzSeries. > > I have tried to look all over the internet for the answer, but I always > gets hits on installing other products using SMP/e. > > We are currently at SMP/E 37.13 > Our SMP/E is 2.4 FMID - HMP1K00. > > What should I do ? > > Thank You > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
