Good to know ahead of time, thanks Rob! I'll be moving to 2.3 early next year
Carmen Vitullo ----- Original Message ----- From: "Rob Scott" <rsc...@rocketsoftware.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Tuesday, October 9, 2018 10:29:22 AM Subject: Re: z/OS 2.3, SDSFAUX missing message... >From the "Summary of changes" section in the SDSF 2.3 manual : As of z/OS V2R3, SDSF requires the SDSF and SDSFAUX address spaces to be active for full functionality. The SDSF address space manages connections, processes ISFPRMxx statements, handles operator commands, and starts and stops SDSFAUX. The SDSFAUX address space is used for data gathering requests. Typically, the SDSF address space is started during IPL using COMMNDxx. During SDSF initialization, the SDSFAUX address space is started. When a user accesses SDSF, the SDSF client program attempts to connect to the SDSF address space. To connect to the SDSF server, the user must have READ access to the ISF.CONNECT.system resource in the SDSF class. If the SDSF address space is not active, SDSF provides limited functionality. The user must have READ access to the SERVER.NOPARM resource in the SDSF class so that ISFPARMS can be used instead of ISFPRMxx. Panels that require the use of the SDSFAUX data gatherers (such as APF, LPA, and LNK) are not available. If the SDSF address is active, but no ISFPRMxx is in effect (such as a syntax error during startup), SDSFAUX is not started. The user requires access to the SERVER.NOPARM resource to fall back to ISFPARMS and requires READ access to the ISF.CONNECT.system resource to continue. Panels that require the use of SDSFAUX are not available. Hope that helps Rob Scott Rocket Software -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Brian France Sent: Tuesday, October 9, 2018 4:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: z/OS 2.3, SDSFAUX missing message... We're in process of upgrading from z/OS 2.1 to 2.3 On our test lpar when we enter sdsf we see the following message - ISF452E SDSFAUX communications failed, return code 0x00000008,, reason code 0x00370801, function "connect". SDSFAUX not available, or function not supported, Indeed we have never run SDSFAUX nor the SDSF server. So any ide'ers as to why this now coming up? Anyone else see it? -- Brian W. France Systems Administrator (Mainframe) Pennsylvania State University Administrative Information Services - Infrastructure/SYSARC Rm 25 Shields Bldg., University Park, Pa. 16802 814-863-4739 b...@psu.edu "To make an apple pie from scratch, you must first invent the universe." Carl Sagan ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ================================ Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy ================================ This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. 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
