Re: Red Alert: Possible corrupted backup copy for z/OS 1.10, 1.11, 1.12 users of zHPF PDSE (2011.01.11)
It would be interesting to hear from one of our list colleagues who might care to post what the D M=DEV() message looks like for a zHPF- enabled device. looks like this: FUNCTIONS ENABLED = MIDAW, ZHPF We do seem to have been hit by the red alert :( We had to IPL two systems after a lot of abends this morning and at first sight it seems to be related... Fortunately none of our production systems have the ptf's mentioned installed. Does anybody know if there is a way to identify the corrupted pdse backups? Regards, Erik Janssen. On Tue, 11 Jan 2011 16:34:07 -0600, Brian Peterson brian.peterson.ibm.m...@comcast.net wrote: I don't have ZHPF-capable DASD either, but according to the messages manual, when you issue D M=DEV(), the last line of the message indicates whether the device supports ZHPF, in the text following FUNCTIONS ENABLED = On my system, I see FUNCTIONS ENABLED = MIDAW According to the messages manual, I would also see ZHPF in this message if zHPF was enabled for this particular device. It would be interesting to hear from one of our list colleagues who might care to post what the D M=DEV() message looks like for a zHPF- enabled device. Brian On Tue, 11 Jan 2011 16:28:04 -0600, Brian Peterson wrote: From the IBM Red Alert 2. The PDSE to be backed up resides on a device which supports zHPF channel programs From this, I believe the answer to your question is you are not affected. All I know is what I've read today in the alerts, however. Brian On Tue, 11 Jan 2011 17:15:43 -0500, Mark Jacobs wrote: I assume that even if your processors support it and it's enabled at the OS level you're not effected if your DASD subsystems don't have the ZHPF feature installed. Is this assumption correct? Mark Jacobs -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Looking for mainframe e-mail software
In listserv%20110002270888.0...@bama.ua.edu, on 01/11/2011 at 10:02 AM, Walt Farrell wfarr...@us.ibm.com said: His initial note said they've decided they needed something that has support. Perhaps they're unwilling to depend on something unsupported/free for some key business process? Paying for support does not guaranty getting it. Using free software does no guaranty that the author won't support it. BTDT,GTTSTS. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Red Alert: Possible corrupted backup copy for z/OS 1.10, 1.11, 1.12 users of zHPF PDSE (2011.01.11)
On Wed, Jan 12, 2011 at 4:15 AM, Erik Janssen erik.jans...@ing.nl wrote: deleted Does anybody know if there is a way to identify the corrupted pdse backups? Regards, Erik Janssen. First thought is to try a restore to a new name. -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Timeout Problem after Switching a DAC unit with OSA in the z10
Before the Christmas break, we moved the TN3270 configuration that was in a DAC unit to z/OS and started using TN3270E as a STC on z/OS using a VIPA address. The environment is as follows: CICS/TS v3.10 with a TOR and an AOR TCP/IP v1.9 z/OS v1.9 Attachmate EXTRA! Enterprise 2000 The problem is that a user is timed out after a 2-3 minutes and it takes the user all the way back to the USSTAB. In CICS I have coded USRDELAY=30 and in the TCP/IP profile parm we coded interval 120 on the TCPCONFIG card. Any and all help is greatly appreciated. *George Rodriguez* *Specialist II - IT Solutions* *Application Support / Quality Assurance* *PX - 47652* *(561) 357-7652 (office)* *(561) 707-3496 (mobile)* *School District of Palm Beach County* *3348 Forest Hill Blvd.* *Room B-332* *West Palm Beach, FL. 33406-5869* *Florida's Only A-Rated Urban District For Six Consecutive Years* Home of Florida's first LEED Gold Certified School Under Florida law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public records request, do not send electronic mail to this entity. Instead, contact this office by phone or in writing. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Windows on zBX
Fairly decent article. http://www.theregister.co.uk/2011/01/12/ibm_zenterprise_zbx_update/ John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Red Alert: Possible corrupted backup copy for z/OS 1.10, 1.11, 1.12 users of zHPF PDSE (2011.01.11)
When zHPF is active, the D M=DEV output is similar to what is shown below. The zHPF indicator is on the last line of output - 07.20.00 d m=dev(6000) 07.20.00 IEE174I 07.20.00 DISPLAY M 092 , C DEVICE 6000 STATUS=ONLINE CHP 5E 5F ENTRY LINK ADDRESS7F70 7F71 DEST LINK ADDRESS 7F78 7F79 PATH ONLINE YN CHP PHYSICALLY ONLINE YY PATH OPERATIONAL YN MANAGED NN CU NUMBER 1300 1300 MAXIMUM MANAGED CHPID(S) ALLOWED: 0 DESTINATION CU LOGICAL ADDRESS = 00 SCP CU ND = 002107.921.EMC.08.000ABWTY.008C SCP TOKEN NED = 002107.900.EMC.08.000ABWTY. 0 SCP DEVICE NED= 002107.900.EMC.08.000ABWTY. FUNCTIONS ENABLED = MIDAW FUNCTIONS ENABLED = ZHPF Also, for zHPF support to be exploited, the Channel Subsystem has to support the option (z10 machines and above), z/OS has to have the option enabled (as previously described) and the DASD subsystem has to have the support loaded and enabled. -Original Message- From: Brian Peterson [mailto:brian.peterson.ibm.m...@comcast.net] Sent: Tuesday, January 11, 2011 5:34 PM Subject: Re: Red Alert: Possible corrupted backup copy for z/OS 1.10, 1.11, 1.12 users of zHPF PDSE (2011.01.11) I don't have ZHPF-capable DASD either, but according to the messages manual, when you issue D M=DEV(), the last line of the message indicates whether the device supports ZHPF, in the text following FUNCTIONS ENABLED = On my system, I see FUNCTIONS ENABLED = MIDAW According to the messages manual, I would also see ZHPF in this message if zHPF was enabled for this particular device. It would be interesting to hear from one of our list colleagues who might care to post what the D M=DEV() message looks like for a zHPF-enabled device. Brian On Tue, 11 Jan 2011 16:28:04 -0600, Brian Peterson wrote: -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
HMC of z/10-BC
IBM has told us that would like us to move our HMC so that they can change the call home server to use the Internet. I am sure there are some white papers and articles about security. Our security dept. is concerned about putting it on the internal network since it is just another Linux box. Can anyone point me to some articles or share their experiences? I have been reading the Intro book on the HMC and it discusses some of the security issues. Andy Pesce z/OS Systems Email: andy.pe...@autozone.com
Re: Red Alert: Possible corrupted backup copy for z/OS 1.10, 1.11, 1.12 users of zHPF PDSE (2011.01.11)
Strange, my output shows FUNCTIONS ENABLED = MIDAW, ZHPF on one line, not two separate lines... This is on both z/os 1.10 and z/os 1.11 Regards, Erik. -Oorspronkelijk bericht- Van: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] Namens Martin Feeney Verzonden: woensdag 12 januari 2011 14:29 Aan: IBM-MAIN@bama.ua.edu Onderwerp: Re: Red Alert: Possible corrupted backup copy for z/OS 1.10, 1.11, 1.12 users of zHPF PDSE (2011.01.11) When zHPF is active, the D M=DEV output is similar to what is shown below. The zHPF indicator is on the last line of output - 07.20.00 d m=dev(6000) 07.20.00 IEE174I 07.20.00 DISPLAY M 092 , C DEVICE 6000 STATUS=ONLINE CHP 5E 5F ENTRY LINK ADDRESS7F70 7F71 DEST LINK ADDRESS 7F78 7F79 PATH ONLINE YN CHP PHYSICALLY ONLINE YY PATH OPERATIONAL YN MANAGED NN CU NUMBER 1300 1300 MAXIMUM MANAGED CHPID(S) ALLOWED: 0 DESTINATION CU LOGICAL ADDRESS = 00 SCP CU ND = 002107.921.EMC.08.000ABWTY.008C SCP TOKEN NED = 002107.900.EMC.08.000ABWTY. 0 SCP DEVICE NED= 002107.900.EMC.08.000ABWTY. FUNCTIONS ENABLED = MIDAW FUNCTIONS ENABLED = ZHPF Also, for zHPF support to be exploited, the Channel Subsystem has to support the option (z10 machines and above), z/OS has to have the option enabled (as previously described) and the DASD subsystem has to have the support loaded and enabled. -Original Message- From: Brian Peterson [mailto:brian.peterson.ibm.m...@comcast.net] Sent: Tuesday, January 11, 2011 5:34 PM Subject: Re: Red Alert: Possible corrupted backup copy for z/OS 1.10, 1.11, 1.12 users of zHPF PDSE (2011.01.11) I don't have ZHPF-capable DASD either, but according to the messages manual, when you issue D M=DEV(), the last line of the message indicates whether the device supports ZHPF, in the text following FUNCTIONS ENABLED = On my system, I see FUNCTIONS ENABLED = MIDAW According to the messages manual, I would also see ZHPF in this message if zHPF was enabled for this particular device. It would be interesting to hear from one of our list colleagues who might care to post what the D M=DEV() message looks like for a zHPF-enabled device. Brian On Tue, 11 Jan 2011 16:28:04 -0600, Brian Peterson wrote: -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html - ATTENTION: The information in this electronic mail message is private and confidential, and only intended for the addressee. Should you receive this message by mistake, you are hereby notified that any disclosure, reproduction, distribution or use of this message is strictly prohibited. Please inform the sender by reply transmission and delete the message without copying or opening it. Messages and attachments are scanned for all viruses known. If this message contains password-protected attachments, the files have NOT been scanned for viruses by the ING mail domain. Always scan attachments before opening them. - -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: HMC of z/10-BC
Andy, There's surprising little about HMC Security. The Intro redbook you found, chapters 5 and 6, were helpful. Your company firewall will be helpful. You'll need to have them enable ports 443 and 9960 for browser support, and possibly port 123 for timer support. You can either integrate the signon ID's with LDAP or define them manually on the HMC. Set up a password rule that reflects your company's rules. Also set timeouts to company rules. Plan how to get console and security logs for the auditors. Plan who will reset passwords. I put a security plan together for our hmc access, but it's heavily customized. I'll try to scrub it and send it to you off list, but give me a few hours. The biggest problem for us was getting people to stop using shared ID's. We did this several months ahead so they had time to adjust. Mary Anne -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Red Alert: Possible corrupted backup copy for z/OS 1.10, 1.11, 1.12 users of zHPF PDSE (2011.01.11)
In the first week of last December our operations team called us with an auxiliary storage shortage on one of our systems, where SMSPDSE1 was occupying about 70% of auxiliary storage. To resolve this situation we restarted SMSPDSE1. We then went over the SYSLOG and OPERLOG and discovered that SMSPDSE1 was stuck in some sort of a recovery routing loop for almost 24 hours, writing OPERLOG records every time and apparently allocating some storage without releasing it. What triggered this was the abends described in OA35260 and OA35296 which occurred the night before, when our HSM migration was running. After the abends, both HSM and SMSPDSE1 kept running normally. We opened a PMR about this problem and are running with a SLIP trap requested by media manager support and PDSE level 2 since then. So far the abends haven't happened again though. As Brian mentioned, we applied these PTFs as part of our regular RSU maintenance... We are now looking into backing off these PTFs, as we really don't want to disable zHPF... Gil. On Wed, Jan 12, 2011 at 12:12 AM, Brian Peterson brian.peterson.ibm.m...@comcast.net wrote: Unfortunately, it appears the PE flag was set for these PTFs just last week, and the initial PTFs in error from August 2010 became RSU1009 (recommended in early October 2010), which gives a window of approximately three months duration where the PTFs were installable as recommended. Folks who performed z/OS maintenance after early October 2010 should carefully check their systems for exposure to this issue. A reminder: To be exposed, you must have 1) applied the PE PTFs, AND 2) actually have PDSE data sets on zHPF-eligible DASD devices. You can issue D IOS,ZHPF to determine whether your system supports zHPF in the first place. At z/OS 1.11 anyway, ZHPF=NO is the default. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Timeout Problem after Switching a DAC unit with OSA in the z10
George If I understand this correctly, you are having a problem between the primary LU application, CICS, and the secondary LU application, the TN3270E server, or involving either CICS, the primary LU application, or the TN3270E server, the secondary LU application. Since you report that the TN3270E client passes from being in communication with CICS - implied - to being presented with the Unformatted System Services (USS) 10 message - assumed to be what you mean by USSTAB, there would appear to be no problem with the TCP connection supporting the TN3270E connection between the TN3270E client and the TN3270E server. But - perhaps being after the break - I realised only slowly what is going on here - and it is, of course, not a *problem* but a *feature*! The clue to your problem is changing from an environment where presumably this feature is not included to one where it is. I know nothing about the DAC unit but I guess it is some sort of outboard TN3270E server. Among the admittedly massive number of TN3270E server parameters - to say nothing of the parameters associated with the z/OS Communications Server (CS) IP component - which incidentally necessarily has the same level as the underlying z/OS - is the INACTIVE statement of the Telnet parameter statements in the Telnet profile: quote 2.10.2.17 INACTIVE Use the INACTIVE parameter statement to define the terminal SNA session inactivity timeout. A connection that has no client-VTAM session activity for the specified time is dropped. Telnet is initialized with a INACTIVE value of 0. The INACTIVE statement can be coded in TELNETGLOBALS, TELNETPARMS, or PARMSGROUP statement blocks. See General rules for parameter statements in topic 2.10.2.1 for more information about the hierarchy of parameter values. Restriction: The INACTIVE statement applies to a KEEPOPEN connection only when an SNA session, with the VTAM application, is active. Telnet uses one timer for the INACTIVE, PRTINACTIVE, and KEEPINACTIVE statements. See z/OS Communications Server: IP Configuration Guide for details. Syntax __ ___ ___ |_INACTIVE 0| |_INACTIVE__sec_| Parameters 0 An INACTIVE timeout value of 0 disables the inactivity timeout. sec Sets the inactivity timeout to the specified number of seconds. When a connection has had no session activity for the specified number of seconds, it is closed. This number must be an integer in the range 0 - 99 999 999. /quote http://publibz.boulder.ibm.com/cgi- bin/bookmgr_OS390/BOOKS/f1a1b471/2.10.2.17 The odd thing is that, by default, this parameter is 0, meaning that the feature is not operational. You must have set it to something like 120 perhaps without realising its significance. It may be relevant that you mention the value of the TCPCONFIG statement INTERVAL parameter which has a default value of 120 - so you didn't need actually to specify 120 - although I personally am in favour of specifying relevant default values as an aid to solving problems when they arise. The mechanism controlled by the INTERVAL parameter of the TCPCONFIG statement[1] is to assure the TCP connection when there is no traffic which otherwise provides that assurance. However your users evidently maintain their TN3270E TCP connection when the timeout you report happens. In order better to understand the issues surrounding - rant I here really do mean issues and ***not*** problems as the word is so widely and flagrantly misused these days /rant - timing with the TN3270E server, I commend section Timers in the chapter on the TN3270E Telnet server in the z/OS CS Configuration Guide: http://publibz.boulder.ibm.com/cgi- bin/bookmgr_OS390/BOOKS/F1A1B371/2.2.1.11 Incidentally, since you took the trouble to mention your level of z/OS, I have kept my quotes and references to V1R9. However I notice there has been some rearrangement of this Timers section in later editions of the manual where it has been relabelled Connection persistence. It is possible - I'd need to check to be sure - that the issues are better expressed in later manuals rather than necessarily including descriptions of new function. Checking your original post in review, I expect that neither CICS parameters nor the TN3270E client are involved since it was the TN3270E server which changed in your configuration. Chris Mason [1] How quaint to refer to a card. I haven't seen an actual card used for customisation in ever such a long time - sometime in the mid '70s I guess. A good friend and colleague who used to visit a lot invariably used cards for aide memoires. He must have intercepted the rubbish disposal at the time the stock of cards where he worked was being thrown out - and there must have been a lot since the stock saw him though to retirement a quarter of a century later! On Wed, 12 Jan 2011 07:48:07 -0500, George Rodriguez george.rodrig...@palmbeachschools.org wrote: Before the Christmas break, we
Re: Timeout Problem after Switching a DAC unit with OSA in the z10
Hi Chris, You're right, quaint is what I would use too about the card... I still own 1 5081 card, that I keep as a reminder of old times. The INACTIVE parm is already coded, Here's what I have: TelnetGlobals TimeMark 1800 ScanInterval 120 TELNETDEVICE 3278-2-E NSX32702 TELNETDEVICE 3278-3-E NSX32703 TELNETDEVICE 3279-3-E NSX32703 TELNETDEVICE 3278-4-E NSX32704 TELNETDEVICE 3279-4-E NSX32704 TELNETDEVICE 3278-5-E NSX32705 TELNETDEVICE 3279-5-E NSX32705 CodePage ISO8859-1 IBM-1047 Inactive 1800 EndTelnetGlobals Anything else you can think of will be greatly appreciated... * * *George Rodriguez* *Specialist II - IT Solutions* *Application Support / Quality Assurance* *PX - 47652* *(561) 357-7652 (office)* *(561) 707-3496 (mobile)* *School District of Palm Beach County* *3348 Forest Hill Blvd.* *Room B-332* *West Palm Beach, FL. 33406-5869* *Florida's Only A-Rated Urban District For Six Consecutive Years* On Wed, Jan 12, 2011 at 10:19 AM, Chris Mason chrisma...@belgacom.netwrote: George If I understand this correctly, you are having a problem between the primary LU application, CICS, and the secondary LU application, the TN3270E server, or involving either CICS, the primary LU application, or the TN3270E server, the secondary LU application. Since you report that the TN3270E client passes from being in communication with CICS - implied - to being presented with the Unformatted System Services (USS) 10 message - assumed to be what you mean by USSTAB, there would appear to be no problem with the TCP connection supporting the TN3270E connection between the TN3270E client and the TN3270E server. But - perhaps being after the break - I realised only slowly what is going on here - and it is, of course, not a *problem* but a *feature*! The clue to your problem is changing from an environment where presumably this feature is not included to one where it is. I know nothing about the DAC unit but I guess it is some sort of outboard TN3270E server. Among the admittedly massive number of TN3270E server parameters - to say nothing of the parameters associated with the z/OS Communications Server (CS) IP component - which incidentally necessarily has the same level as the underlying z/OS - is the INACTIVE statement of the Telnet parameter statements in the Telnet profile: quote 2.10.2.17 INACTIVE Use the INACTIVE parameter statement to define the terminal SNA session inactivity timeout. A connection that has no client-VTAM session activity for the specified time is dropped. Telnet is initialized with a INACTIVE value of 0. The INACTIVE statement can be coded in TELNETGLOBALS, TELNETPARMS, or PARMSGROUP statement blocks. See General rules for parameter statements in topic 2.10.2.1 for more information about the hierarchy of parameter values. Restriction: The INACTIVE statement applies to a KEEPOPEN connection only when an SNA session, with the VTAM application, is active. Telnet uses one timer for the INACTIVE, PRTINACTIVE, and KEEPINACTIVE statements. See z/OS Communications Server: IP Configuration Guide for details. Syntax __ ___ ___ |_INACTIVE 0| |_INACTIVE__sec_| Parameters 0 An INACTIVE timeout value of 0 disables the inactivity timeout. sec Sets the inactivity timeout to the specified number of seconds. When a connection has had no session activity for the specified number of seconds, it is closed. This number must be an integer in the range 0 - 99 999 999. /quote http://publibz.boulder.ibm.com/cgi- bin/bookmgr_OS390/BOOKS/f1a1b471/2.10.2.17 The odd thing is that, by default, this parameter is 0, meaning that the feature is not operational. You must have set it to something like 120 perhaps without realising its significance. It may be relevant that you mention the value of the TCPCONFIG statement INTERVAL parameter which has a default value of 120 - so you didn't need actually to specify 120 - although I personally am in favour of specifying relevant default values as an aid to solving problems when they arise. The mechanism controlled by the INTERVAL parameter of the TCPCONFIG statement[1] is to assure the TCP connection when there is no traffic which otherwise provides that assurance. However your users evidently maintain their TN3270E TCP connection when the timeout you report happens. In order better to understand the issues surrounding - rant I here really do mean issues and ***not*** problems as the word is so widely and flagrantly misused these days /rant - timing with the TN3270E server, I commend section Timers in the chapter on the TN3270E Telnet server in the z/OS CS Configuration Guide: http://publibz.boulder.ibm.com/cgi- bin/bookmgr_OS390/BOOKS/F1A1B371/2.2.1.11 Incidentally, since you took the trouble to mention your level of z/OS, I have kept my quotes and references to V1R9. However I notice there has been some rearrangement of this Timers section
speculation: z/OS enhancments
OK. I'm not sure if this is off-topic or not. If it is, then I apologize. But I'm wondering if z/OS is lacking in some areas. Or limited in some way that you wish would disappear. I'm assuming that cost is not a problem. Which is a stupid assumption, of course. Possible examples, which are just examples without justification. JCL enhancements: Make a JCL enhancement or replacement so that it would be more like a scripting language. The ability to have a DO loop. Or trap JCL errors. Or arithmetic in // SET commands within a DO loop (perhaps a // LET ?). Job names 8 characters. Larger set of characters to be valid in a job name (such as lower case and _). Step names 8 characters. More valid characters, again such as lower case. JES job token which is guaranteed to be unique within a JES MAS forever. Perhaps based on the STCKE value in some way. And put this token in every SMF record so that each SMF record can be related to a specific, unique, JES entity. Perhaps this should even be universally unique, not just with a MAS or just for a JES managed job but for any and every possible executable entity. Basically so that I know which SMF records belong together and not have any confusion. Yes, it does happen that the SMF joblog jobname+reader start date/time is not unique. I've done it. Support FBA, at least for non-legacy datasets which do not need hardware keys such as VSAM, PDSE, etc. Support sequential files via ACB interface. It would simplify AMODE(31) coding. Implement a Linux ABI emulation layer in z/OS UNIX to allow Linux/s390x executable programs to run under z/OS UNIX. Granted, they'd still be ASCII based, but it might be worth it. Implement something in z/OS UNIX akin to the Linux /proc pseudo filesystem. A JES UNIX pseudo filesystem which allows access to JES SPOOL as if it were a UNIX filesystem. Perhaps via SAPI interface so that those RACF profiles are used for access. John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: HMC of z/10-BC
I think that being 'just another Linux box' is not an accurate description in a security context. The box -is- Linux, but I believe that it is better described as an 'appliance' or 'system console'. It should be viewed as a integral component of the zbox, not as a standalone 'workstation'. These terms have meaning to most auditors and they tend to leave them alone. More, the HMC's appear to be prepared to endure scans and probes without ill effect. I agree that the HMC (and support elements) should not be on a company network, and should not be dependent on any other network component (LDAP servers, for example). A very private 'command and control' infrastructure seems to be an acceptable solution. Of course, access to that infrastructure would be restricted. I'm pretty sure that the Internet connections are outbound only initiated by a local human or via the POTS line. I believe that to be pretty easy to set up in a firewall. HTH and good luck. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Pesce, Andy Sent: Wednesday, January 12, 2011 8:02 AM To: IBM-MAIN@bama.ua.edu Subject: HMC of z/10-BC IBM has told us that would like us to move our HMC so that they can change the call home server to use the Internet. I am sure there are some white papers and articles about security. Our security dept. is concerned about putting it on the internal network since it is just another Linux box. Can anyone point me to some articles or share their experiences? I have been reading the Intro book on the HMC and it discusses some of the security issues. Andy Pesce z/OS Systems Email: andy.pe...@autozone.com NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: HMC of z/10-BC
On Wed, 12 Jan 2011 08:54:57 -0600, Mary Anne Matyaz wrote: Your company firewall will be helpful. You'll need to have them enable ports 443 and 9960 for browser support, and possibly port 123 for timer support. I haven't been paying attention. May I infer that via HMC and STP, z can now be a full egalitarian NTP player, client as well as server? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: HMC of z/10-BC
There are some very specific ports that have to opened on the firewall for the call home to work. IBM does not try to access from outside. I have to see if I have the docs around somewhere. But an IBM IPR or CE should be able to provide the exact setup. I know of many users who access the HMC on the network, and remotely via VPN. Never any issues. Doug On 1/12/2011 9:01 Pesce, Andy wrote: IBM has told us that would like us to move our HMC so that they can change the call home server to use the Internet. I am sure there are some white papers and articles about security. Our security dept. is concerned about putting it on the internal network since it is just another Linux box. Can anyone point me to some articles or share their experiences? I have been reading the Intro book on the HMC and it discusses some of the security issues. Andy Pesce z/OS Systems Email: andy.pe...@autozone.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Timeout Problem after Switching a DAC unit with OSA in the z10
George Well, I've been having another look at your problem mainly because the description of the INACTIVE parameter says that the TN3270E TCP connection is dropped, by which we may assume the author means, disconnected. I'm wondering if maybe there has been a failure properly to describe the result of reaching an INACTIVE time limit in the light of the introduction of functions appearing after this descriptive text was written. - Should the authors reflect the later functions in the description of the INACTIVE statement? Yes. - Do they ever? There are safer bets! There is a section in the z/OS Communications Server Configuration Guide which describes the behaviour of a TN3270E concatenation - SNA session to TN3270E TCP connection - when the session ends. This is Figure 64. Session ending scenarios in section 2.2.1.8.1 Session initiation management (LOGAPPL, QINIT, FIRSTONLY, and DEFONLY). http://publibz.boulder.ibm.com/cgi- bin/bookmgr_OS390/BOOKS/f1a1b371/2.2.1.8.1 According to this logic diagram, the following would be required in order that your TN3270E clients would leave the CICS application and be presented with an USS 10 message: - The expiry of the value of the INACTIVE statement would need to be regarded as a Logoff rather than a Break - You would need to have specified LUSESSIONPEND rather than the default NOLUSESSIONPEND. - You would need to have specified one of the following: -- DEFAULTAPPL cics LOGAPPL -- DEFAULTAPPL cics FIRSTONLY LOGAPPL -- DEFAULTAPPL cics FIRSTONLY QINIT The expiry of the value of the INACTIVE statement being regarded as a Logoff rather than a Break makes sense if one appreciates that there was nothing wrong with the SNA session. It's just that one of the session partner LUs, the TN3270E server, decided to call it a day! The alternative to being presented with the USS 10 message is for the session with your CICS to be re-established at, I assume, whatever point is normal when you first establish the session with CICS. Note that the default for the DEFAULTAPPL statement LOGAPPL and FIRSTONLY parameters (QINIT does not appear really to be relevant) is for the action when the parameters are not specified to apply - naturally enough - and this would cause that alternative to happen. This implies that you have specified the LOGAPPL parameter. Please report back on whichever of these circumstances fits your situation even if, in checking it out, you solve your problem. Chris Mason On Wed, 12 Jan 2011 09:19:46 -0600, Chris Mason chrisma...@belgacom.net wrote: George If I understand this correctly, you are having a problem between the primary LU application, CICS, and the secondary LU application, the TN3270E server, or involving either CICS, the primary LU application, or the TN3270E server, the secondary LU application. Since you report that the TN3270E client passes from being in communication with CICS - implied - to being presented with the Unformatted System Services (USS) 10 message - assumed to be what you mean by USSTAB, there would appear to be no problem with the TCP connection supporting the TN3270E connection between the TN3270E client and the TN3270E server. But - perhaps being after the break - I realised only slowly what is going on here - and it is, of course, not a *problem* but a *feature*! The clue to your problem is changing from an environment where presumably this feature is not included to one where it is. I know nothing about the DAC unit but I guess it is some sort of outboard TN3270E server. Among the admittedly massive number of TN3270E server parameters - to say nothing of the parameters associated with the z/OS Communications Server (CS) IP component - which incidentally necessarily has the same level as the underlying z/OS - is the INACTIVE statement of the Telnet parameter statements in the Telnet profile: quote 2.10.2.17 INACTIVE Use the INACTIVE parameter statement to define the terminal SNA session inactivity timeout. A connection that has no client-VTAM session activity for the specified time is dropped. Telnet is initialized with a INACTIVE value of 0. The INACTIVE statement can be coded in TELNETGLOBALS, TELNETPARMS, or PARMSGROUP statement blocks. See General rules for parameter statements in topic 2.10.2.1 for more information about the hierarchy of parameter values. Restriction: The INACTIVE statement applies to a KEEPOPEN connection only when an SNA session, with the VTAM application, is active. Telnet uses one timer for the INACTIVE, PRTINACTIVE, and KEEPINACTIVE statements. See z/OS Communications Server: IP Configuration Guide for details. Syntax __ ___ ___ |_INACTIVE 0| |_INACTIVE__sec_| Parameters 0 An INACTIVE timeout value of 0 disables the inactivity timeout. sec Sets the inactivity timeout to the specified number of seconds. When a connection has had no session activity for the specified number of seconds, it is closed. This number must be an
Re: HMC of z/10-BC
That is my understanding Paul, though we are not doing that yet. The HMC can be an NTP server or can use another NTP server in your network. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: speculation: z/OS enhancments
If you really want any of this stuff, build a business case and submit it to IBM. Sending a wish list to IBM-MAIN won't get it done. Frankly, I'd like code that did what I meant and not what I said, but I'm not holding my breath for it. For example, what business problem will jobnames GT 8 characters solve? What's the benefit to your organization? What's the business justification to do it? Will you convert to UNIX if the jobname restriction isn't changed? If it is changed, will it improve your profitability or productivity? Will it improve IBM's profitability or sell more copies of z/OS? Bob Shannon Rocket Software -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: speculation: z/OS enhancments
On Wed, Jan 12, 2011 at 9:53 AM, McKown, John john.mck...@healthmarkets.com wrote: OK. I'm not sure if this is off-topic or not. If it is, then I apologize. But I'm wondering if z/OS is lacking in some areas. Or limited in some way that you wish would disappear. I'm assuming that cost is not a problem. Which is a stupid assumption, of course. Possible examples, which are just examples without justification. JCL enhancements: Make a JCL enhancement or replacement so that it would be more like a scripting language. The ability to have a DO loop. Or trap JCL errors. Or arithmetic in // SET commands within a DO loop (perhaps a // LET ?). deleted You could run a TSOBATCH job and execute a non-ISPF clist within it. My suggestions: When a SMS volume is set to DISNEW, consider the volume to have no space in calculating free space for the storage group, and try to migrate to ML1/2 in every hourly migration. When a SMS volume is set to DISALL, migrate MIG(0) to other primary volumes if not in use. When a SMS volume is set to DISABLE ALLOCATION (DISALC), allow opens to datasets on that volume only if already open. If dataset is not allocated, perform MIG(0) to another primary volume before opening. This would clear a volume after a short shutdown and restart of application that is using it. (Kind of like integrating LDMP into SMS). Create some sort of similar status setting for non-SMS volumes. -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: speculation: z/OS enhancments
So you're basically saying that it is off-topic. Gotcha. I'm not whining. Just talking. Or curious. Sorry. John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Bob Shannon Sent: Wednesday, January 12, 2011 10:41 AM To: IBM-MAIN@bama.ua.edu Subject: Re: speculation: z/OS enhancments If you really want any of this stuff, build a business case and submit it to IBM. Sending a wish list to IBM-MAIN won't get it done. Frankly, I'd like code that did what I meant and not what I said, but I'm not holding my breath for it. For example, what business problem will jobnames GT 8 characters solve? What's the benefit to your organization? What's the business justification to do it? Will you convert to UNIX if the jobname restriction isn't changed? If it is changed, will it improve your profitability or productivity? Will it improve IBM's profitability or sell more copies of z/OS? Bob Shannon Rocket Software -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Timeout Problem after Switching a DAC unit with OSA in the z10
Hi Chris, Now I'm 100% confused... It's probably the way I'm describing the problem. Let me show you examples of messages that CICS provides when things happen: This is for user TARANTI: CICPTOR is the CICS that owns the terminals. 06:28:42 TELNE870 Signon this is the initial startup 06:35:53 TELNE875 Signon 7 minutes later the user is signing in again 06:35:59 TELNE875 Signon a few seconds later signing on again 06:36:16 TELNE875 Signon 07:08:38 TELNE875 Signoff 07:32:50 TELNE870 Signoff 07:59:58 TELNE1B0 Signon 08:00:02 TELNE1B0 Signon 09:21:44 TELNE1B0 Signoff 09:51:38 TELNE933 Signon 11:57:24 TELNE51A Signon 11:57:27 TELNE51A Signon 12:01:04 TELNE933 Signoff CICPTM is the CICS where the application is. 07:06:20 TELNE875 timed out if the initial start up is at 6:28 and inactivity happens 30 min. later, this is ok 07:30:09 TELNE870 timed out 09:18:27 TELNE1B0 timed out 11:57:51 TELNE933 timed out 12:42:42 TELNE51A timed out I appreciate your help... * * *George Rodriguez* *Specialist II - IT Solutions* *Application Support / Quality Assurance* *PX - 47652* *(561) 357-7652 (office)* *(561) 707-3496 (mobile)* *School District of Palm Beach County* *3348 Forest Hill Blvd.* *Room B-332* *West Palm Beach, FL. 33406-5869* *Florida's Only A-Rated Urban District For Six Consecutive Years* On Wed, Jan 12, 2011 at 11:19 AM, Chris Mason chrisma...@belgacom.netwrote: George Well, I've been having another look at your problem mainly because the description of the INACTIVE parameter says that the TN3270E TCP connection is dropped, by which we may assume the author means, disconnected. I'm wondering if maybe there has been a failure properly to describe the result of reaching an INACTIVE time limit in the light of the introduction of functions appearing after this descriptive text was written. - Should the authors reflect the later functions in the description of the INACTIVE statement? Yes. - Do they ever? There are safer bets! There is a section in the z/OS Communications Server Configuration Guide which describes the behaviour of a TN3270E concatenation - SNA session to TN3270E TCP connection - when the session ends. This is Figure 64. Session ending scenarios in section 2.2.1.8.1 Session initiation management (LOGAPPL, QINIT, FIRSTONLY, and DEFONLY). http://publibz.boulder.ibm.com/cgi- bin/bookmgr_OS390/BOOKS/f1a1b371/2.2.1.8.1 According to this logic diagram, the following would be required in order that your TN3270E clients would leave the CICS application and be presented with an USS 10 message: - The expiry of the value of the INACTIVE statement would need to be regarded as a Logoff rather than a Break - You would need to have specified LUSESSIONPEND rather than the default NOLUSESSIONPEND. - You would need to have specified one of the following: -- DEFAULTAPPL cics LOGAPPL -- DEFAULTAPPL cics FIRSTONLY LOGAPPL -- DEFAULTAPPL cics FIRSTONLY QINIT The expiry of the value of the INACTIVE statement being regarded as a Logoff rather than a Break makes sense if one appreciates that there was nothing wrong with the SNA session. It's just that one of the session partner LUs, the TN3270E server, decided to call it a day! The alternative to being presented with the USS 10 message is for the session with your CICS to be re-established at, I assume, whatever point is normal when you first establish the session with CICS. Note that the default for the DEFAULTAPPL statement LOGAPPL and FIRSTONLY parameters (QINIT does not appear really to be relevant) is for the action when the parameters are not specified to apply - naturally enough - and this would cause that alternative to happen. This implies that you have specified the LOGAPPL parameter. Please report back on whichever of these circumstances fits your situation even if, in checking it out, you solve your problem. Chris Mason On Wed, 12 Jan 2011 09:19:46 -0600, Chris Mason chrisma...@belgacom.net wrote: George If I understand this correctly, you are having a problem between the primary LU application, CICS, and the secondary LU application, the TN3270E server, or involving either CICS, the primary LU application, or the TN3270E server, the secondary LU application. Since you report that the TN3270E client passes from being in communication with CICS - implied - to being presented with the Unformatted System Services (USS) 10 message - assumed to be what you mean by USSTAB, there would appear to be no problem with the TCP connection supporting the TN3270E connection between the TN3270E client and the TN3270E server. But - perhaps being after the break - I realised only slowly what is going on here - and it is, of course, not a *problem* but a *feature*! The clue to your problem is changing from an environment where presumably this feature is not included to one where it is. I know nothing about the DAC unit but I guess it is some sort of outboard TN3270E server.
Re: passing instream sysin to next step
If it were any other DD besides SYSIN, I would definitely consider it. However, SYSIN for IEBGENER is reserved for command parms and input to IEBGENER. Additionally, as John M pointed out, there are potentially 3 or 4 other overrides for the current STEP1. If STEP1 suddenly becomes an IEBGENER, the overrides are lost for the subsequent step. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: passing instream sysin to next step
Easily solved by making the new first step name STEP0 or COPYDATA or any other unique name. The instream input data would then have to go into STEP0.SYSUT1 or COPYDATA.SYSUT1 of course, not SYSIN. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ken Moore Sent: Wednesday, January 12, 2011 12:34 PM To: IBM-MAIN@bama.ua.edu Subject: Re: passing instream sysin to next step If it were any other DD besides SYSIN, I would definitely consider it. However, SYSIN for IEBGENER is reserved for command parms and input to IEBGENER. Additionally, as John M pointed out, there are potentially 3 or 4 other overrides for the current STEP1. If STEP1 suddenly becomes an IEBGENER, the overrides are lost for the subsequent step. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DLF - DLFCLASS Using DLF for PDS data?
Graham; Yes, it could be converted to a PDSE. It does not appear that even VLF can be used simply by creating a class for the object and then activating that parmlib member. It appears that the application must be modified to use the VLF macros to define and connect to the object. It is vendor product code that is accessing the dataset so changing code is not possible. I am assuming from that sparse response on this list that VLF/DLF expertise is still being grown. An interesting, funny, sidelight is one of their previous system programmers had put SYS1.IMAGELIB in the linklist to take advantage of the VLF/LLA performance improvement. I don't have any data as to whether there were any actual performance improvements for SYS1.IMAGELIB doing this. I would be able to tell in one day if there were improvements doing this for the customer PDS (and no it does not contain any executable code). I have read everything that is available not on VLF install and planning and it is still ambiguous on if it can be used to cache datasets for general across the board access. any info appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: passing instream sysin to next step
On Tue, 11 Jan 2011 15:44:20 -0800, Cris Hernandez #9 wrote: I agree with this post. Why read the same file twice other than to make a copy of it, especially when it's something as easily corruptible as raw, instream data coded within JCL. What makes instream data so easily corruptible? Well, OK, as recently as yesterday I typed SAVE with my cursor in the data rather than on the command line. (I recovered in time.) But how does adding an IEBGENER step make the process more resistant to this or any such error compared to simply reading the SYSIN twice (if that were possible)? Related question: Long ago an Expert told me it was forbidden to open SYSIN, read it, close it, reopen it and read it again in the same step. (I had asked him why he preceded a Waterloo SCRIPT step with IEBGENER to a temp DSN.) By recent experience, I can reread SYSIN (within a single step). Has something changed, or was my mentor mistaken long ago? (I think it was MVS 3.8.) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DLF - DLFCLASS Using DLF for PDS data?
Ricc, Yes the COFx macros must be used by the application to benefit from the VLF cache - obviously CSV does this on our behalf for LLA program management. Unless the PDS members you are referring to is LOADed, there is little VLF can help with actually caching the member contents without changes to the application. You can measure VLF class performance using SMF-41 records. You can investigate performance benefits for LLA versus PGM fetch for individual programs by using the CSVLLIX1 exit. (I believe you are an MXI G2 customer, hence you can use the VLF and LLA commands to see the performance data interactively without having to author your own SMF41 post-processing report or CSVLLIX1 exit.) Rob Scott Lead Developer Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.2305 Email: rsc...@rs.com Web: www.rocketsoftware.com -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ricc Harding Sent: 12 January 2011 17:44 To: IBM-MAIN@bama.ua.edu Subject: Re: DLF - DLFCLASS Using DLF for PDS data? Graham; Yes, it could be converted to a PDSE. It does not appear that even VLF can be used simply by creating a class for the object and then activating that parmlib member. It appears that the application must be modified to use the VLF macros to define and connect to the object. It is vendor product code that is accessing the dataset so changing code is not possible. I am assuming from that sparse response on this list that VLF/DLF expertise is still being grown. An interesting, funny, sidelight is one of their previous system programmers had put SYS1.IMAGELIB in the linklist to take advantage of the VLF/LLA performance improvement. I don't have any data as to whether there were any actual performance improvements for SYS1.IMAGELIB doing this. I would be able to tell in one day if there were improvements doing this for the customer PDS (and no it does not contain any executable code). I have read everything that is available not on VLF install and planning and it is still ambiguous on if it can be used to cache datasets for general across the board access. any info appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: passing instream sysin to next step
If it were any other DD besides SYSIN, I would definitely consider it. However, SYSIN for IEBGENER is reserved for command parms and input to IEBGENER. Additionally, as John M pointed out, there are potentially 3 or 4 other overrides for the current STEP1. If STEP1 suddenly becomes an IEBGENER, the overrides are lost for the subsequent step. -- Easily solved by making the new first step name STEP0 or COPYDATA or any other unique name. The instream input data would then have to go into STEP0.SYSUT1 or COPYDATA.SYSUT1 of course, not SYSIN. Not only that but you could use DDNAME= for your input on SYSIN. For example //SYSIN DD DDNAME=MYINPUT Or //SYSUT1 DD DDNAME=MYINPUT Then they could override MYINPUT to point to instream or a dataset. A new first step as point out of STEP0 or COPYDATA would not override any other JCL already coded. And the DDNAME could give you more flexibility of standardization. Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: speculation: z/OS enhancments
My personal first law of data processing is ... the principal activity of data processing is processing data So if you ever see the law again please credit me Avram Friedman. Now it follows that if processing data is so important then effective enhancements must improve, enhance or support the need for processing data. The enhancement history of z/OS and its family tree has always been driven by data base (data processing) requirements. VS to allow for more job concurrancy. SVS-MVS to get rid of over engineered SUs and better intergrate new technology like VSAM which by the way is a collection of Access Methods (read data processing) MVS SE to address VSCR concerns that were occuring in large IMS and CICS shops. etc etc It is interesting that the original poster of this thread suggested JCL as something that could be enhanced. The following story was once frequently told by people who worked for Amdahl including my self. One of the things that maide the IBM 360 a sucess was abandonment of the idea of specialized instruction sets for example geared to Business or Scientific data processing, NOT BOTH. THe 360 instruction set was a marvel. It actually made it possible to code in assembler with packed arithmatic, even a pack instruction and there data movement break throughs like the MVCL instruction. It however was badly timed inovation. Second and third generation lanuage like Fortran and Cobol were just taking hold. Hardware design changed from processing one instruction per cycle to pipelining, ie processing parts of several instructions ever cycle ... one instruction might be getting fetched while a diffrent instruction was having its OPCODE decoded. Cycle times were reduced and a finished instruction was pumped out almost every cycle. At the time I use to say A Ford leaves the assembley line in Dearborn MI every 15 seconds but every one knows it does not take 15 seconds to build a Ford. Now the IBM 360 was the worlds worse instruction set for pipelineing. The same thing thiat made it easy to write assembler code (advanced instructions) made it a bear to design hardware for (instructions that made it difficult to pipeline because RX and SS instructions were so diffrent). So why did Amdahl design a plug compatable copy of what was then a known bad design? Amdahl is often quoted as saying No one would buy a bigger, faster, more cost effective machine if they had to re-write all there JCL Best wishes Avram Friedman Not there from the begining but an old man never the less. On Wed, 12 Jan 2011 09:53:17 -0600, McKown, John john.mck...@healthmarkets.com wrote: OK. I'm not sure if this is off-topic or not. If it is, then I apologize. But I'm wondering if z/OS is lacking in some areas. Or limited in some way that you wish would disappear. I'm assuming that cost is not a problem. Which is a stupid assumption, of course. Possible examples, which are just examples without justification. JCL enhancements: Make a JCL enhancement or replacement so that it would be more like a scripting language. The ability to have a DO loop. Or trap JCL errors. Or arithmetic in // SET commands within a DO loop (perhaps a // LET ?). Job names 8 characters. Larger set of characters to be valid in a job name (such as lower case and _). Step names 8 characters. More valid characters, again such as lower case. JES job token which is guaranteed to be unique within a JES MAS forever. Perhaps based on the STCKE value in some way. And put this token in every SMF record so that each SMF record can be related to a specific, unique, JES entity. Perhaps this should even be universally unique, not just with a MAS or just for a JES managed job but for any and every possible executable entity. Basically so that I know which SMF records belong together and not have any confusion. Yes, it does happen that the SMF joblog jobname+reader start date/time is not unique. I've done it. Support FBA, at least for non-legacy datasets which do not need hardware keys such as VSAM, PDSE, etc. Support sequential files via ACB interface. It would simplify AMODE(31) coding. Implement a Linux ABI emulation layer in z/OS UNIX to allow Linux/s390x executable programs to run under z/OS UNIX. Granted, they'd still be ASCII based, but it might be worth it. Implement something in z/OS UNIX akin to the Linux /proc pseudo filesystem. A JES UNIX pseudo filesystem which allows access to JES SPOOL as if it were a UNIX filesystem. Perhaps via SAPI interface so that those RACF profiles are used for access. John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy
IBM's mainframe-blade hybrid to do Windows
http://www.theregister.co.uk/2011/01/12/ibm_zenterprise_zbx_update/ IBM's mainframe-blade hybrid to do WindowsAlertPrint Post comment Retweet FacebookTighter server coupling coming? http://www.theregister.co.uk/2011/01/12/ibm_zenterprise_zbx_update/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Looking for mainframe e-mail software
More than just e-mail, Lotus Notes and Domino. Here's pointers to more info if you'd like it. Here's a flyer: ftp://public.dhe.ibm.com/common/ssi/ecm/en/lob14026usen/LOB14026USEN.PDF Here's the sw web page for Lotus Notes and Domino http://www-01.ibm.com/software/lotus/products/domino/ Here's a December 2010 paper by Gerald Hosch (IBM Boe) about consolidation of Lotus Domino and Lotus Notes to Linux on System z ftp://public.dhe.ibm.com/common/ssi/ecm/en/zsw03072usen/ZSW03072USEN.PDF HTH. Regards, Pam C -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Timeout Problem after Switching a DAC unit with OSA in the z10
George Some percentage of your confusion may be removed when you appreciate that my responses do not emerge fully outfitted from the head of Zeus but take a while to compose - while I find the appropriate references, for example. Thus my second post was a continuation of my first post in reply to your original post and, in case this is the source of your confusion, nothing to do with your first response. However, I believe I am now the one with a right to be confused. Which product is it that is producing the messages with the TELNE prefix? You appear to associate them with CICS so it would imply that whatever product is creating the messages has something to do with CICS. It was implicit in my previous two responses that the TN3270E to which you referred in your original post was the z/OS Communications Server (CS) TN3270E server. Indeed you then post a subset of the TN3270E parameters. I am aware that there are CICS signon and signoff transactions, CESN and CESF, IIRC. I suppose that some product could be logging these transactions. But then the mystery deepened as I noticed that the signon and signoff messages had a numeric part which looked as if it might be some sort of 3- digit channel address ... I actually had a few more points to raise following your second post giving the TELNETGLOBALS block but I think I need some clarification over what your current configuration is - and what your previous configuration was. Also, if you really are using the z/OS CS TN3270E server, I think the whole of the TN3270E PROFILE should be included - with two limitations: 1. Be sure that the TN3270E PROFILE file contains *only* the TN3270E statements. I believe, given that you would have recently set it up, this will be the case. 2. If you have masses of mapping statements, supply only a set relevant to one of the TN3270E clients with which you are having a problem. In case it is not clear, the reason I find your third post no help whatsoever is that it seems to imply CICS is in some sort of way supporting the TN3270E server function. This is not what I expected at all. All CICS should be able to see is a session, when it starts, when it stops and why it stops and, of course, any transactions the end user runs. I was going to say that CICS is quite unaware that the SNA session supported by CICS is concatenated to a TN3270E TCP connection. If it is presented with a control vector X'64' (CV64) in the exit used to initiate the SNA session, it will know that way beyond the TN3270E server is a logical continuation of the session associated with an IP address and a port number and, if the TN3270E server has been induced to use the resolver in order to translate the IP address into a name to go with the IP address. In any case, whatever the configuration, you will need to identify exactly which event is causing the ending of the association between CICS and whatever is supporting the TN3270E function in such a way that the USS 10 message appears. Those CICS messages are no help I'm afraid. You should be looking at logs for all the components involved and, if nothing shows up, taking traces for the relevant components in whatever order seems most likely to be productive. You are fortunate that you appear to have a reproducible problem. Chris Mason On Wed, 12 Jan 2011 12:26:52 -0500, George Rodriguez george.rodrig...@palmbeachschools.org wrote: Hi Chris, Now I'm 100% confused... It's probably the way I'm describing the problem. Let me show you examples of messages that CICS provides when things happen: This is for user TARANTI: CICPTOR is the CICS that owns the terminals. 06:28:42 TELNE870 Signon this is the initial startup 06:35:53 TELNE875 Signon 7 minutes later the user is signing in again 06:35:59 TELNE875 Signon a few seconds later signing on again 06:36:16 TELNE875 Signon 07:08:38 TELNE875 Signoff 07:32:50 TELNE870 Signoff 07:59:58 TELNE1B0 Signon 08:00:02 TELNE1B0 Signon 09:21:44 TELNE1B0 Signoff 09:51:38 TELNE933 Signon 11:57:24 TELNE51A Signon 11:57:27 TELNE51A Signon 12:01:04 TELNE933 Signoff CICPTM is the CICS where the application is. 07:06:20 TELNE875 timed out if the initial start up is at 6:28 and inactivity happens 30 min. later, this is ok 07:30:09 TELNE870 timed out 09:18:27 TELNE1B0 timed out 11:57:51 TELNE933 timed out 12:42:42 TELNE51A timed out I appreciate your help... * * *George Rodriguez* *Specialist II - IT Solutions* *Application Support / Quality Assurance* *PX - 47652* *(561) 357-7652 (office)* *(561) 707-3496 (mobile)* *School District of Palm Beach County* *3348 Forest Hill Blvd.* *Room B-332* *West Palm Beach, FL. 33406-5869* *Florida's Only A-Rated Urban District For Six Consecutive Years* On Wed, Jan 12, 2011 at 11:19 AM, Chris Mason chrisma...@belgacom.netwrote: George Well, I've been having another look at your problem mainly because the description of the INACTIVE parameter says that the TN3270E TCP connection is
Re: speculation: z/OS enhancments
On Wed, 12 Jan 2011 12:21:35 -0600, Avram Friedman wrote: One of the things that maide the IBM 360 a sucess was abandonment of the idea of specialized instruction sets for example geared to Business or Scientific data processing, NOT BOTH. The Floating-point feature was included for scientific processing. The Decimal feature was included for business processing? Both instruction sets were included so that IBM could market a single architecture suitable for either kind of processing. One factor may have been that they didn't want to have to write and maintain two operating systems on two different architectures. It was not expected that the business users would use floating-point instructions or that scientific users would use packed decimal. THe 360 instruction set was a marvel. It actually made it possible to code in assembler with packed arithmatic, even a pack instruction and there data movement break throughs like the MVCL instruction. Move Long was introduced with system/370, not 360. Hardware design changed from processing one instruction per cycle to pipelining, ie processing parts of several instructions ever cycle ... I don't know when processors started to pipeline instructions. The 360-91 had a pipelined processor. Early 360 machines did not. Now the IBM 360 was the worlds worse instruction set for pipelineing. Bold assertion. Do you have any data to back that up? So why did Amdahl design a plug compatable copy of what was then a known bad design? Known bad design? Dr. Amdahl was the chief architect of the System/360. He left IBM and started Amdahl corporation because he wanted to extend the series with a higher performance processor and IBM did not think that it would be marketable. And BTW, it was not a copy. It was a compatible processor, but it was implemented differently. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: speculation: z/OS enhancments
m42tom-ibmm...@yahoo.com (Tom Marchant) writes: Bold assertion. Do you have any data to back that up? 360 allowed self-modifying instruction ... potentially instructions already in the pipeline. one of the claims for Amdahl macro-code was that it was essentially 370 with some tweaks ... including precluding self-modifying. even in some number of (non-cache, non-pipeline) 360s that did i-fetch a double word (or more at time) ... there was extra overhead in constantly checking whether there was storage alteration to address that was already fetched by the instruction unit (within the same double word). harvard architectures with split instruction and data caches w/o cache concistency get some processing performance by i-cache ignoring standard storage alterations. in the case of store-in data cache ... program loaders that may operate on instruction streams ... making alterations that appear in d-cache. before initiating exection ... the loader then executes special operation that explicitly forces d-cache alterated lines to main storage and invalidates possible corresponding i-cache lines. with the force of altered data (from d-cache) to storage and invalidation of corresponding addresses in i-cache ... subsequent instruction stream references to those addressed would be forced to fetch the contents from storage (explicit programming required to support alteration of potential instructions). harvard architecture with i-cache operation ignoring standard storage alterations ... is much easier to pipeline and easier to scaleup multiprocessor (not only being able to ignore storage alterations on the same processor ... but also able to ignore standard storage alterations on all the other processors). -- virtualization experience starting Jan1968, online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: speculation: z/OS enhancments
On Wed, Jan 12, 2011 at 3:00 PM, Tom Marchant m42tom-ibmm...@yahoo.com wrote: On Wed, 12 Jan 2011 12:21:35 -0600, Avram Friedman wrote: deleted Hardware design changed from processing one instruction per cycle to pipelining, ie processing parts of several instructions ever cycle ... I don't know when processors started to pipeline instructions. The 360-91 had a pipelined processor. Early 360 machines did not. The Strech / IBM 7030 was the first computer with accelerator technologies. http://www-03.ibm.com/ibm/history/exhibits/mainframe/mainframe_PP7030.html They were loosing money at US$10M in 1960 dollars per copy. It read from 6 different magnetic core units at the same time. deleted So why did Amdahl design a plug compatable copy of what was then a known bad design? deleted http://en.wikipedia.org/wiki/Gene_Amdahl -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: FTP-IBM
anyone having problems on Maint download from IBM ftp server?? -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. American General is a trademark owned by American International Group, Inc., and is being used under license. American General Finance, Inc. is no longer an affiliate of American International Group, Inc. or the American General Life Companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: passing instream sysin to next step
ok, let's back up to the beginning. why would anyone want to put their data into a SYSIN DD * ? doesn't sound like anything that would happen in a production environment, or QA testing, so that leaves unit testing in development, ad hoc reporting and classroom exercises. If it isn't production or Quality Assurance, do whatever suits you, but the answer to your questions... how to corrupt your in-stream data: 1) edit with ISPF - caps on-off - change all's - accidental keystrokes - datatype, lrecl restrictions - unprintable characters - TSO inexperience - inadvertant tabs, spacing Copying the data to a flat file keeps the raw data separate and somewhere it won't be lost or edited unless editing is required, plus its reusable by other JCL members. --- On Wed, 1/12/11, Paul Gilmartin paulgboul...@aim.com wrote: From: Paul Gilmartin paulgboul...@aim.com Subject: Re: passing instream sysin to next step To: IBM-MAIN@bama.ua.edu Date: Wednesday, January 12, 2011, 12:56 PM On Tue, 11 Jan 2011 15:44:20 -0800, Cris Hernandez #9 wrote: I agree with this post. Why read the same file twice other than to make a copy of it, especially when it's something as easily corruptible as raw, instream data coded within JCL. What makes instream data so easily corruptible? Well, OK, as recently as yesterday I typed SAVE with my cursor in the data rather than on the command line. (I recovered in time.) But how does adding an IEBGENER step make the process more resistant to this or any such error compared to simply reading the SYSIN twice (if that were possible)? Related question: Long ago an Expert told me it was forbidden to open SYSIN, read it, close it, reopen it and read it again in the same step. (I had asked him why he preceded a Waterloo SCRIPT step with IEBGENER to a temp DSN.) By recent experience, I can reread SYSIN (within a single step). Has something changed, or was my mentor mistaken long ago? (I think it was MVS 3.8.) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: passing instream sysin to next step
On Wed, Jan 12, 2011 at 3:01 PM, Cris Hernandez #9 hernandez...@yahoo.comwrote: ok, let's back up to the beginning. why would anyone want to put their data into a SYSIN DD * ? doesn't sound like anything that would happen in a production environment, or QA testing, so that leaves unit testing in development, ad hoc reporting and classroom exercises. happens frequently in production on restarts with a dd override. If it isn't production or Quality Assurance, do whatever suits you, but the answer to your questions... how to corrupt your in-stream data: 1) edit with ISPF - caps on-off - change all's - accidental keystrokes - datatype, lrecl restrictions - unprintable characters - TSO inexperience - inadvertant tabs, spacing Copying the data to a flat file keeps the raw data separate and somewhere it won't be lost or edited unless editing is required, plus its reusable by other JCL members. --- On Wed, 1/12/11, Paul Gilmartin paulgboul...@aim.com wrote: From: Paul Gilmartin paulgboul...@aim.com Subject: Re: passing instream sysin to next step To: IBM-MAIN@bama.ua.edu Date: Wednesday, January 12, 2011, 12:56 PM On Tue, 11 Jan 2011 15:44:20 -0800, Cris Hernandez #9 wrote: I agree with this post. Why read the same file twice other than to make a copy of it, especially when it's something as easily corruptible as raw, instream data coded within JCL. What makes instream data so easily corruptible? Well, OK, as recently as yesterday I typed SAVE with my cursor in the data rather than on the command line. (I recovered in time.) But how does adding an IEBGENER step make the process more resistant to this or any such error compared to simply reading the SYSIN twice (if that were possible)? Related question: Long ago an Expert told me it was forbidden to open SYSIN, read it, close it, reopen it and read it again in the same step. (I had asked him why he preceded a Waterloo SCRIPT step with IEBGENER to a temp DSN.) By recent experience, I can reread SYSIN (within a single step). Has something changed, or was my mentor mistaken long ago? (I think it was MVS 3.8.) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: speculation: z/OS enhancments
At 15:00 -0600 on 01/12/2011, Tom Marchant wrote about Re: speculation: z/OS enhancments: One of the things that maide the IBM 360 a sucess was abandonment of the idea of specialized instruction sets for example geared to Business or Scientific data processing, NOT BOTH. The Floating-point feature was included for scientific processing. The Decimal feature was included for business processing? Both instruction sets were included so that IBM could market a single architecture suitable for either kind of processing. One factor may have been that they didn't want to have to write and maintain two operating systems on two different architectures. It was not expected that the business users would use floating-point instructions or that scientific users would use packed decimal. I may be mis-remembering but I seem to have the impression that one of the features (I think scientific) was optional on the lowest level model (the 360/30). This did not affect the Operating System but only what you could run on that version of the machine if you did not have the feature. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: speculation: z/OS enhancments
At 09:53 -0600 on 01/12/2011, McKown, John wrote about speculation: z/OS enhancments: OK. I'm not sure if this is off-topic or not. If it is, then I apologize. But I'm wondering if z/OS is lacking in some areas. Or limited in some way that you wish would disappear. I'm assuming that cost is not a problem. Which is a stupid assumption, of course. Mine is to fix/enhance the ENQs for datasets so they include the volume name as part of the RNAME. The original use of DSN in lieu of DSN+VOLSER was OK until GRS and/or Shared DASD was introduced and you could have multiple datasets with the same DSN in your complex. There are some components (such as SPF EDIT) that do it right by actually using the VOLSER to tell the difference between multiple datasets with the same name. The show stopper in fixing this is that Initiation does not bother to do its DISP ENQs by looking up the VOLSER when it does its ENQ in support of DISP=OLD/SHR. Also enhance ENQ so an EXCLUSIVE ENQ owner can switch itself to SHR ownership (and thus allow backed up other tasks who are waiting for it to release to start running). The current inability to downgrade from EXC to SHR status leads to such design flaws as Job Streams that have STEP1 with a DISP=OLD and subsequent Steps with DISP=SHR holding exclusive ownership of the Dataset Name (not the Dataset Itself - see the lack of Volser as part of the RNAME above for details) until at least the end of the last step referencing the DSN. I say at least since I think that early release is what occurs now when originally the ENQ was held (even when not needed) until Job End. This makes jobs that might run for an hour but only need the DISP=OLD lock for the first minute or two lock out other DISP=SHR job streams for the full hour (when they would already be running if the DISP=OLD step were not there). Side-Comment - The fix for EXC-SHR is IMO a VERY simple thing to implement. You update the ENQ Macro Parms to have a flag to say EXC-SHR (like the one that does SHR-EXC [what this is supposed to be used for is a question with the lack of being unable to do anything except DEQ when you are done with your upgraded EXC state if you even get it - What you are supposed to use this SHR-EXC ability for is a separate issue]). When issued, the code just resets the ENQ chain entry to show that the task has SHR status now and then drives the DEQ code that runs the chain releasing waiting SHR tasks until running off the chain or encountering a waiting EXC request. I can see some potentially minor support issues if you try to issue such an ENQ on a system that does not support it (ie: What happens if you send such an ENQ to a down level version of the ENQ routine? Will it ignore the flag it does not know, return a RC [which the user's code can ignore by just continuing as EXC as currently would occur], or ABEND the task [a bad thing]). The ABEND case can be handled by just having a CVT flag that says the support is there (as there are other such flags) and the user's program can not bother playing good-guy and issuing the ENQ TYPE=MAKE-SHR when the support is not there. Since the Initiator code to make use of this enhancement would COREQ the ENQ upgrade there would be no possibility for the Initiator code running on a non-supporting system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: passing instream sysin to next step
not when I ran production... but I suspect you're talking about a short control card sysin, something easily CC'd in SPF edit, not raw data input. haven't seen raw data in a production JCL stream since we parted with punch cards circa 1980. if other folk's mainframe shops still run that way, I'll reiterate putting the data safely into a flat file before running batch against. --- On Wed, 1/12/11, Sam Siegel s...@pscsi.net wrote: From: Sam Siegel s...@pscsi.net Subject: Re: passing instream sysin to next step To: IBM-MAIN@bama.ua.edu Date: Wednesday, January 12, 2011, 6:36 PM On Wed, Jan 12, 2011 at 3:01 PM, Cris Hernandez #9 hernandez...@yahoo.comwrote: ok, let's back up to the beginning. why would anyone want to put their data into a SYSIN DD * ? doesn't sound like anything that would happen in a production environment, or QA testing, so that leaves unit testing in development, ad hoc reporting and classroom exercises. happens frequently in production on restarts with a dd override. If it isn't production or Quality Assurance, do whatever suits you, but the answer to your questions... how to corrupt your in-stream data: 1) edit with ISPF - caps on-off - change all's - accidental keystrokes - datatype, lrecl restrictions - unprintable characters - TSO inexperience - inadvertant tabs, spacing Copying the data to a flat file keeps the raw data separate and somewhere it won't be lost or edited unless editing is required, plus its reusable by other JCL members. --- On Wed, 1/12/11, Paul Gilmartin paulgboul...@aim.com wrote: From: Paul Gilmartin paulgboul...@aim.com Subject: Re: passing instream sysin to next step To: IBM-MAIN@bama.ua.edu Date: Wednesday, January 12, 2011, 12:56 PM On Tue, 11 Jan 2011 15:44:20 -0800, Cris Hernandez #9 wrote: I agree with this post. Why read the same file twice other than to make a copy of it, especially when it's something as easily corruptible as raw, instream data coded within JCL. What makes instream data so easily corruptible? Well, OK, as recently as yesterday I typed SAVE with my cursor in the data rather than on the command line. (I recovered in time.) But how does adding an IEBGENER step make the process more resistant to this or any such error compared to simply reading the SYSIN twice (if that were possible)? Related question: Long ago an Expert told me it was forbidden to open SYSIN, read it, close it, reopen it and read it again in the same step. (I had asked him why he preceded a Waterloo SCRIPT step with IEBGENER to a temp DSN.) By recent experience, I can reread SYSIN (within a single step). Has something changed, or was my mentor mistaken long ago? (I think it was MVS 3.8.) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: speculation: z/OS enhancments
On Wed, 12 Jan 2011 12:21:35 -0600, Avram Friedman wrote: So why did Amdahl design a plug compatable copy of what was then a known bad design? Amdahl is often quoted as saying No one would buy a bigger, faster, more cost effective machine if they had to re-write all there JCL And yet, some are buying other machines on the premise that they're bigger, faster, [or] more cost effective (frequent topic on this list). And, as you say, they're not rewriting all their JCL; they're discarding it and saying, Good riddance! But, to the OP: More sophisticated flow control such as looping is totally contrary to the JCL paradigm which presumes the complete static analysis of resource requirements. Consider particularly JES3 which presumes that every job step will be executed, regardless of COND or IF. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: speculation: z/OS enhancments
So perhaps what would be more desirable would be an alternative to JCL. But that's not likely. I can and do use Dovetailed Technologies' Co:Z to run local UNIX shell commands and scripts in a job. So I can just continue to use that. In any case, as you pointed out about JES3, there are the automated job restart packages such as CA-11 which would die a horrible death if JCL is changed too much. I know I'm off topic a bit, but I wonder what UNIX shops use to do things which CA-11 does does for batch? Or is it like in the olden days where the restart is manual or built into the script itself? This lack of automated restart was a major clang! when a vendor was touting a conversion from z/OS to Windows. They promised to convert all JCL to some scripting package. On Wed, 2011-01-12 at 17:51 -0600, Paul Gilmartin wrote: On Wed, 12 Jan 2011 12:21:35 -0600, Avram Friedman wrote: So why did Amdahl design a plug compatable copy of what was then a known bad design? Amdahl is often quoted as saying No one would buy a bigger, faster, more cost effective machine if they had to re-write all there JCL And yet, some are buying other machines on the premise that they're bigger, faster, [or] more cost effective (frequent topic on this list). And, as you say, they're not rewriting all their JCL; they're discarding it and saying, Good riddance! But, to the OP: More sophisticated flow control such as looping is totally contrary to the JCL paradigm which presumes the complete static analysis of resource requirements. Consider particularly JES3 which presumes that every job step will be executed, regardless of COND or IF. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- John McKown Maranatha! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: speculation: z/OS enhancments
m42tom-ibmm...@yahoo.com (Tom Marchant) writes: Dr. Amdahl was the chief architect of the System/360. He left IBM and started Amdahl corporation because he wanted to extend the series with a higher performance processor and IBM did not think that it would be marketable. And BTW, it was not a copy. It was a compatible processor, but it was implemented differently. during the ill-fated Future System effort ... anything that smacked of internal competition was killed ... resulted in 370 product pipeline going dry ... which is attributed with allowing clone manufactures to gain market foothold. in the wake of Future System demise there was mad rush to get products back into the 370 product pipeline ... with 3033 going on in parallel with 3081/370xa effort. The 3033 started out as 168 wiring diagram mapped to 20% faster chips ... which also had 10 times circuits/chip (with only 10 percent being used) ... however, there was eventually some redesign before 3033 shipped to better utilize higher density on-chip ... eventually resulting in being 50% faster. This talks about 3081 using some of the FS technology resulting in circuits/mip (and therefor manufacturing costs) being significant higher than clone processors: http://www.jfsowa.com/computer/memo125.htm other details about FS mentioned here (including the FS failure casting dark shadow over the corporation for decades) http://www.cs.clemson.edu/~mark/fs.html there are claims that Amdahl knew nothing about the FS effort (occuring after he left). however he gave a talk at MIT in large auditorium in the early 70s on his new company. During the talk he was asked how he convinced investors to fund his company. He said something about customers had already invested couple hundred billion in 360-based software and even if IBM were to completely walk away from 360 (could be considered a veiled reference to FS), that was large enough install base to keep him in business through the end of the century. -- virtualization experience starting Jan1968, online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
hwkeytool and IBM contact for support
Hello folks, I have been struggling to use hwkeytool (supplied with Java 6 SDK for z/OS) . I want to make it an alternative to some homemade C routines we have here for key management. The reasons are obvious - every small change in our cripto requirements is a pita to change these programs, recompile them, etc. Specifically I have been upset about hwkeytool behaviour on the - importkeystore command parameter. Anybody has some experience on this tool or may point to any internal IBMer that may be able to exchange a few e-mails to clarify my doubts? Regards, Henrique Seganfredo -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: passing instream sysin to next step
happens frequently in production on restarts with a dd override. I am not criticising, but I don't understand your reply. - Ted MacNEIL eamacn...@yahoo.ca -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: passing instream sysin to next step
On Wed, Jan 12, 2011 at 6:23 PM, Ted MacNEIL eamacn...@yahoo.ca wrote: happens frequently in production on restarts with a dd override. I am not criticising, but I don't understand your reply. No criticism taken. I'm just talking about a dd override in the jcl to change control cards or other 80 data. Could be bad information in a sequential dataset that is quicker and easier to fix by using instream data from a dd override when a deadline is approaching. With in stream data, you can insert the correct data without having to run a one off job to update a production data set name. Assuming the sysout is archived it is documented that an override occurred. It is not for everyday usage but for on-call, application down, situations. Let me know if you want more details. Cheers, Sam - Ted MacNEIL eamacn...@yahoo.ca -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: passing instream sysin to next step
At 14:31 -0600 on 01/11/2011, McKown, John wrote about Re: passing instream sysin to next step: STEP1 may have other DDs in it which the user is used to overriding with //STEP1.ddname DD and so that would require a JCL change for all users of the PROC. Curiously, as I recall, OS/VS1's JES work-alike allowed the DSN referback to SYSIN and SYSOUT of a previous step. For SYSIN, it reread the input. For SYSOUT, it did the equivalent of a DISP=MOD. Is this for a single program or for a number of different programs? If it is for a single program than reassemble it to use SYSIN1 in lieu of SYSIN. Now write a top-hat program that reads from SYSIN (not caring if it is a DSN= or *) and writes it to a DSN=DSN,DISP=(MOD,PASS) dataset. When done, it XTMLs to the real program (or ATTACHs it). The second step can just DSN=DSN,DISP=(OLD,PASS). -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
z/OS 1.11 upgrade - WLM couple datasets
Hi All, I am the one who raise this issue and Allan Staller has answered my question. After that the issue has gone side-way, off what I am after. To clarify my original query, my concern has nothing to do with Master Catalog regarding the new WLM couple data sets. As we have a simplex sysplex here with 2 lpars(Devt and Prod), obviously we cannot upgrade both at the same time. As the lpars share the same WLM couple data sets, we could live with not changing any policy on z/OS 1.11 in Devt but only if we have to on Prod which should still be z/OS 1.9. As explained by Marna Walles, the policy, service class and workload informations have changed in length ,eg 168 to 360 see below. Thus new WLM data sets are required. Sorry for the long post, extract from Marna Walles S2223. Reallocate the WLM couple data set (Required-IF as of R10) Required if the current WLM couple data set is not significantly larger than required for the currently used WLM. service definition so that the data set can accommodate the increased size of the WLM policy structures. In z/OS V1R10, you might need a larger workload management (WLM) couple data set because the WLM servide class and workload records in the WLM policy are longer, as shown below. IWMSVPOL entry Pre-z/OS V1R10 entry length z/OS V1R10 entry length Policy information 168 360 Service Class 64 144 Workload40 112 Regard, Sue - IMPORTANT NOTICE : The information in this email is confidential and may also be privileged. If you are not the intended recipient, any use or dissemination of the information and any disclosure or copying of this email is unauthorised and strictly prohibited. If you have received this email in error, please promptly inform us by reply email or telephone. You should also delete this email and destroy any hard copies produced. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/OS 1.11 upgrade - WLM couple datasets
On 01/11/2011 08:53 AM, Mark Zelden wrote: On Tue, 11 Jan 2011 00:22:27 -0600, Brian Westerman brian_wester...@syzygyinc.com wrote: If that's what works for you then by all means you should stick with it. I have performed literally hundreds of upgrades and I have never kept the old master catalog as the master for the new system. Mostly it has to do with properly setting up the master catalog in the first place. The only datasets in the master catalog should be those that get shipped with the new OS, the rest should be in usercats. Wow! That is a surprise coming from someone who has done that many. I guess this is a religious issue. I too have performed hundreds of upgrades and I never bother creating a new master catalog just to add a couple of new data sets that are needed. What are you gaining? If it's cleanup, then there is a problem to begin with because there shouldn't be junk in the master catalog. There are often more than a few, but often those data sets are for products / features that won't be used anyway, so who cares that they sit on the sysres uncatalogged (I never catalog MSYS for example). The last 2 times I created new master cats were for MVS/ESA 5.2 , since sharing was allowed after that. Then I went to new master catalogs for some systems after IBM told us that IMBED / REPLICATE would not be allowed in the future (which we all know now that IBM reversed that SOD, so I went through all that trouble for nothing). I can see where you would be able to keep things going for quite a while with system symbols for most of the important datasets, but eventually you are going to have a bunch of useless entries in your master catalog or things will move and you'll end up taking the chance that you will miss it. There seems to be a lot of chance for things to go wrong, and with all of the other issues involved in a migration, making it more complex, for me, is not a good thing. I don't understand this. What symbols are required for important data sets? I use symbols to refer to system specific data sets in PARMLIB members for example, but I am not really using SYMBOLICRELATE. What can go wrong when you aren't changing anything (except cataloging a new required data set for LNKLST / LPA for example)? Yes, if you are sloppy and never uncatalog data sets that go away with a new OS version, then you will have some dead entries. In the grand scheme of things, even a large amount (FSVO large) doesn't hurt anything. BTW, every migration manual tells you the list of dsns that are no longer part of the OS. But even without that, a simple VTOC compare will tell you the ones you can uncatalog after all your MCAT sharing systems have been migrated.I always keep a $CLEANUP member in my install PDS with activities that need to be done after migration. Even if I used a new master catalog there would be plenty of other post migration activities. Uncataloging a few data sets that are no longer shipped is minor. As I said though, if what you are currently doing works for you, then almost by definition it's correct, for you. Just because I feel it adds complexity, doesn't make me right, in the end, whatever works correctly is what is right. Agree 100% there. Not saying I'm correct either, just debating. But I admit I have a really hard time seeing there other side's point of view in this one. :-) On the other hand, if you are not using symbols and you are really reusing the same physical page datasets etc. then that's playing with fire. I don't understand this either. Are you saying there is some potential harm in IPLing a new version of the OS using previously formatted page data sets? Cheers, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ... When I first starting doing MVS installs and migration, at that point the recommended method was to create a new master catalog, so we got used to doing it that way and when that recommendation was relaxed we didn't see any reason to change a procedure that was working. I suspect the preferred approach may have something to do with how many MVS images you run; and if you have multiple images in a sysplex sharing a master catalog and install with rolling IPL, then changing the master catalog would make things much more complicated. We only have a single production image, so a new MVS version can't really be tested under load without going live and putting all production on it at once. That is always done on a weekend, and although it is rare, there have been a few instances over the last 25 years where we were forced to back out an upgrade. Call us paranoid, but we don't want any of the minimal system pieces that must be present and functional to IPL the production system on the old release of MVS, like the old
Re: z/OS 1.11 upgrade - WLM couple datasets
I have performed literally hundreds of upgrades and I have never kept the old master catalog as the master for the new system. Sue is right, answer the question or start a new thread. I have also asked this one or two times in the past. Kees. For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/OS 1.11 upgrade - WLM couple datasets
Sue Chiam sue.ch...@qbe.com wrote in message news:of1dd3566c.9aac17b8-onca257817.001ede8b-ca257817.001fe...@qbe.com ... Hi All, I am the one who raise this issue and Allan Staller has answered my question. After that the issue has gone side-way, off what I am after. To clarify my original query, my concern has nothing to do with Master Catalog regarding the new WLM couple data sets. As we have a simplex sysplex here with 2 lpars(Devt and Prod), obviously we cannot upgrade both at the same time. As the lpars share the same WLM couple data sets, we could live with not changing any policy on z/OS 1.11 in Devt but only if we have to on Prod which should still be z/OS 1.9. As explained by Marna Walles, the policy, service class and workload informations have changed in length ,eg 168 to 360 see below. Thus new WLM data sets are required. Sue, Another concern regarding WLM and the 1.11 upgrade is the PDS in which WLM definitions a saved. If we save our definitions under 1.11, we can't read them anymore on 1.10 and the same will apply to your 1.9 system, so you must do saves on 1.9 until you are fully migrated to 1.11. This is not documented in the 1.11 migrations docs. Several z/OS versions are mentioned to have changed the layout of the tables in the PDS, but 1.11 is *not* mentioned there. However I have the problem between 1.10 and 1.11. Kees. For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
