Re: PF9 Swap question
In 4de1283a.7020...@ync.net, on 05/28/2011 at 11:52 AM, Rick Fochtman rfocht...@ync.net said: It may have been a controller function, but I distinctly remember configuring ISPF to show error indicators in read and changes in yellow. Yes, but not on a 3278. It's possible that ISPF still generates the color attributes if you specify the terminal type as 3278 but are actually using a different terminal. -- 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: Antwort: Differences between REGION=0K and REGION=0M
Mark Zelden m...@mzelden.com wrote in message news:listserv%201105271425023543.0...@bama.ua.edu... On Fri, 27 May 2011 14:56:01 -0400, Tony Harminc t...@harminc.net wrote: On 27 May 2011 12:42, Charles Mills charl...@mcn.org wrote: REGION=0K requests only one-thousandth as much as REGION=0M. Does SPACE=(TRK,0) allocate only 1/15 as much DASD as SPACE=(CYL,0)? Generally yes. But it could be different on older devices with a different number of tracks/cylinder. Where you *really* have to be careful is if you have a 3390-0. Then the amount of space you get is undefined. Tony H. on Friday I picture a newbie searching google or the archives in the future being very confused by this thread. :-) -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS Correct, the topic is REGION. If someone likes to change the topic to TRK, create a new thread. If someone likes to change the topic to giving the most funny and useless answers, create a new List. Thanks, 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: INOPERATIVE PATH
Hi, thanks for your anwsers. The inoperative path appeared in devices (3490) tha are physsicaly at our other site. Both sites are connected through a DWDM network with FICON cascading. Lizette: The affected CHPIDs are 06 and 96, have a closer look at the IOS450E. The DS P, shows that the path through 06 and 96 the are inoperative (). The D M=CHP(06) shows that the paths are not operational ($). We have checked close to every hardware component (fibers, SFPs,...) involved in the path to the CU, and everything seems to be working OK. My question was why can paths get inoperative without a meaningful infrastructural change. We upgrade one z10 to z196, but the IOS appeared in LPARs in the old z10, where nothing was changed. Thanks in advance. Regards, Christian. -- 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: WAS abend - SDC3
Jags In amongst a mass of APAR hits, Googling websphere dc3 abend turned up the following as hit number 8: http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp? topic=/com.ibm.websphere.messages.doc/abend.html reorganised quote Table 1. WebSphere Application Server for z/OS abend codes Abend code: DC3 Abend Reason: 000C0008 Explanation: An error occurred which results in the region being terminated with this abend reason code. Suggested Action: Look in the error log for information regarding a previous error which led to the region being terminated. /reorganised quote It would appear you simply need to examine your log for an earlier problem. If you still have a problem, you might like to seek out a list more focused on WebSphere than IBM-MAIN. Unfortunately my feeble attempts at Googling with the purpose of finding such a list failed utterly! Maybe someone else would be kind enough to identify which barrel is hiding this particular light. Chris Mason On Mon, 30 May 2011 11:27:34 +0530, jagadishan perumal jagadish...@gmail.com wrote: Hi, We tried bring up the address space related to WAS. One region was up but another control region BBOS001 ended up with an abend : BPXP018I THREAD 0CD64260, IN PROCESS 83886280, ENDED 343 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 4FDC3000, AND REASON CODE 000C0008. IEF450I BBOS001 BBOS001 - ABEND=SDC3 U REASON=000C0008 344 TIME=10.54.35 Could anyone please guide. Regards, Jags -- 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: Mainframe C Link Step Error - using pthread (POSIX)
On Fri, 27 May 2011 12:10:33 -0700, John Weber j...@fiteq.com wrote: Here is the link step. Thanks! 77 //LKED EXEC PGM=HEWL,COND=(4,LT,COMPILE), 78 //REGION=LREGSIZ,PARM='LPARM' 79 //SYSLIB DD DSNAME=TCPIP.SEZACMTX,DISP=SHR 80 // DD DSNAME=LIBPRFX..SCEELKED,DISP=SHR 81 //SYSPRINT DD SYSOUT=* 82 //SYSLIN DD DSNAME=*.COMPILE.SYSLIN,DISP=(OLD,DELETE) 83 // DD DDNAME=SYSIN 84 //SYSLMOD DD DSNAME=OUTFILE 85 //SYSUT1 DD UNIT=TUNIT.,SPACE=TSPACE. 86 //SYSINDD DUMMY Looks like you may be missing the CEE.SCEELKEX May depend on if you use the prelinker or not... or CEE.SCEELIB if you use XPLINK. Cheers, Jantje. -- 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: WAS abend - SDC3
Hi Chris, I googled it and found that some threads were not allowing the started task to start. Are there any way to kill the OMVS threads ? On Mon, May 30, 2011 at 3:57 PM, Chris Mason chrisma...@belgacom.netwrote: Jags In amongst a mass of APAR hits, Googling websphere dc3 abend turned up the following as hit number 8: http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp? topic=/com.ibm.websphere.messages.doc/abend.html reorganised quote Table 1. WebSphere Application Server for z/OS abend codes Abend code: DC3 Abend Reason: 000C0008 Explanation: An error occurred which results in the region being terminated with this abend reason code. Suggested Action: Look in the error log for information regarding a previous error which led to the region being terminated. /reorganised quote It would appear you simply need to examine your log for an earlier problem. If you still have a problem, you might like to seek out a list more focused on WebSphere than IBM-MAIN. Unfortunately my feeble attempts at Googling with the purpose of finding such a list failed utterly! Maybe someone else would be kind enough to identify which barrel is hiding this particular light. Chris Mason On Mon, 30 May 2011 11:27:34 +0530, jagadishan perumal jagadish...@gmail.com wrote: Hi, We tried bring up the address space related to WAS. One region was up but another control region BBOS001 ended up with an abend : BPXP018I THREAD 0CD64260, IN PROCESS 83886280, ENDED 343 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 4FDC3000, AND REASON CODE 000C0008. IEF450I BBOS001 BBOS001 - ABEND=SDC3 U REASON=000C0008 344 TIME=10.54.35 Could anyone please guide. Regards, Jags -- 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: WAS abend - SDC3
Table 1. WebSphere Application Server for z/OS abend codes Abend code: DC3 Abend Reason: 000C0008 Explanation: An error occurred which results in the region being terminated with this abend reason code. Suggested Action: Look in the error log for information regarding a previous error which led to the region being terminated. /reorganised quote Jags Websphere like MQ or DB2 rely on the Reason Code to indicate the problem. Try googling 000C0008 and websphere. I found many hits that might make sense. For instance, for WAS 1.5 there is http://www-01.ibm.com/support/docview.wss?uid=swg1PK19006 The DC3 is probably the common abend code for WAS. The Return Code is actually going to indicate the issue. You should also have supporting errors in the JOBLOG or SYSLOG for this problem. You did not indicate the level of z/OS or WAS so it is difficult to suggest any more. IBM has newsgroups for Websphere and MQ called Developer Newsgroups. http://www.ibm.com/developerworks/forums/wsdd_forums.jspa You can try there. 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: INOPERATIVE PATH
Christian, Sorry about not reading the IOS450E correctly. It is easier if when posting you remove the continuation numbers of the MLTWO. Sometimes if you just nudge a connection ever so slightly then the point to point light is misaligned and one or both of the machines could not see it. So if the z10 was producing the messages that might mean that it was looking down the pipe to the other end and just not seeing it. It does not always mean that the z10 is the problem. Only that the z10 sees the problem. I also have a DWDM. One of two paths failed for my ETR. It took the CE several months to determine it was a bad card in the DWDM. Our z10 did not see an issue, our z9 saw the issue. And the error message were only on the z9 side. And we did everything. Replaced ficon, reset connections, checked the cisco router in the middle. And so forth. Still in my case, the CE had to replace cards in the DWDM one at a time on both sides before it was found. Hardware and cables can be delicate. It does not always take much of a mis-alignment for one side or the other to start producing IOS messages. 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: Excessive CPU usage in SDSF
I noticed this once and when I looked at the operator he was banging the enter key to refresh the display several times a second. Easy enough to check and if so a little OJT might be all you need. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of ??? ?? ??? Sent: Sunday, May 29, 2011 4:05 AM To: IBM-MAIN@bama.ua.edu Subject: Excessive CPU usage in SDSF Hi, One of our operators is using excessive CPU. Most of his time is spent running the printer, and he is usually looking at the output queue in SDSF. There are a few filters specified in SDSF and the information is sorted in a special way. He keeps rising to the top of the CPU consumption list. Moving him to a lower service class doesn't always work. We are using z/OS 1.11 and JES2. Has anyone seen something like this? -- 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: WAS abend - SDC3
START BBO6ACR,JOBNAME=BBOS001,ENV=ZOSB.ZOSB.BBOS001 BBODMNB – was up BBOS001 – Produced the below error . START BBO6DMN,JOBNAME=BBODMNB,ENV=ZOSB.ZOSB.BBODMNB BBOO0024I ERRORS WILL BE WRITTEN TO CERR FOR JOB BBOS001. BBOO0302I REGION REQUESTED = 0K 886 ACTUAL BELOW/ABOVE LINE LIMIT = 8M / 1847M ABOVE BAR FREE/ALLOC ADDR = 0 / 0 BBOO0201I JVM HEAP INFORMATION FOR SERVER BBOC001/BBOS001/STC05755 BBOO0202I (STC05755) HEAP(MATURE), COUNT(), FREE STORAGE( 891 7F8AA30), TOTAL STORAGE( 800) BBOO0204I JVM HEAP INFORMATION FOR SERVER BBOC001/BBOS001/STC05755 892 COMPLETE BBOO0035W TERMINATING THE CURRENT PROCESS, REASON=C9C21C4F. BPXP018I THREAD 0CD8ABF9, IN PROCESS 67109087, ENDED 928 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 04DC3000, AND REASON CODE 000C0008. BPXP018I THREAD 0CD89CE8, IN PROCESS 67109087, ENDED 930 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 04DC3000, AND REASON CODE 000C0008. BPXP018I THREAD 0CD88DD7, IN PROCESS 67109087, ENDED 932 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 04DC3000, AND REASON CODE 000C0008. BPXP018I THREAD 0CD87EC6, IN PROCESS 67109087, ENDED 934 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 04DC3000, AND REASON CODE 000C0008. BPXP018I THREAD 0CD86FB5, IN PROCESS 67109087, ENDED 936 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 04DC3000, AND REASON CODE 000C0008. BPXP018I THREAD 0CD81552, IN PROCESS 67109087, ENDED 938 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 04DC3000, AND REASON CODE 000C0008. BPXP018I THREAD 0CD80641, IN PROCESS 67109087, ENDED 940 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 04DC3000, AND REASON CODE 000C0008. BPXP018I THREAD 0CD64260, IN PROCESS 67109087, ENDED 942 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 4FDC3000, AND REASON CODE 000C0008. IEF450I BBOS001 BBOS001 - ABEND=SDC3 U REASON=000C0008 943 On Mon, May 30, 2011 at 5:02 PM, Lizette Koehler stars...@mindspring.comwrote: Table 1. WebSphere Application Server for z/OS abend codes Abend code: DC3 Abend Reason: 000C0008 Explanation: An error occurred which results in the region being terminated with this abend reason code. Suggested Action: Look in the error log for information regarding a previous error which led to the region being terminated. /reorganised quote Jags Websphere like MQ or DB2 rely on the Reason Code to indicate the problem. Try googling 000C0008 and websphere. I found many hits that might make sense. For instance, for WAS 1.5 there is http://www-01.ibm.com/support/docview.wss?uid=swg1PK19006 The DC3 is probably the common abend code for WAS. The Return Code is actually going to indicate the issue. You should also have supporting errors in the JOBLOG or SYSLOG for this problem. You did not indicate the level of z/OS or WAS so it is difficult to suggest any more. IBM has newsgroups for Websphere and MQ called Developer Newsgroups. http://www.ibm.com/developerworks/forums/wsdd_forums.jspa You can try there. 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 -- 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: WAS abend - SDC3
We tried bring up the address space related to WAS. One region was up but another control region BBOS001 ended up with an abend : BPXP018I THREAD 0CD64260, IN PROCESS 83886280, ENDED 343 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 4FDC3000, AND REASON CODE 000C0008. Jags There is a good redbook on debugging WAS http://www.redbooks.ibm.com/redpapers/pdfs/redp6880.pdf It has details on how to go about debugging problems in WAS. For the BBO0024I message BBOO0024I ERRORS WILL BE WRITTEN TO CERR FOR JOB BBOS001. BBOO0024I ERRORS WILL BE WRITTEN TO string string. Explanation: WebSphere for z/OS will be using the indicated repository for logging errors. For file repositories,the file is obtained from the BBOERROR DD specification. If no such specification is provided, and a system logger stream has been specified, the log stream will be used for logging errors. If logging to the designated file or log stream can not be done, then CERR will be used for error logging. Note that CERR is equivalent to SYSOUT by default. There may be interesting messages in this file CERR for your issue. This may be a unix file. 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: INOPERATIVE PATH
As other collegues mentioned,there are many reasons you may see these messages.If there is FICON Director and these are shared by any device that you have touched its connection,it makes sense. An IFCC error can cause inoperative path to connections that you did not do any change even. You might have checked these already but better to mention : 1-Any device in this conenction or sharing these connections have the minimum microcode level installed or not - SPAR guide and exception letter from resourcelink 2-Checking which channels you got IFCC error from HMC as well.IBM can understand details from this information. 3-Having HW CE do a function test to cards. Better is have HW CE check error messages and get help from IBM and DWDM provider both as SW and HW. There is one command with path that IBM did as FICON RAS enhancement that shows more in detail reasons of inoperative path ( D M=DEV(,(ch)) ) where device number ch is channel number. This shows RNID information Check for IOS2001I and IOS2002I and and RNID information .Related APAR is OA13644,OA10906 Just to share experience:( Better is always get help from HW and SW support,because cases can be different and working on troubleshotting of IOS related messages are sometimes dangerous ) Sometimes even all microcode levels are ok,cards are ok (if HW CEs did a function test on cards on z10 and DWDM and everything seems working fine) you may see inoperative path messages after this kind of work. Then posibble cause can be FICON cables plug/unplug without making paths offline to devices from z/OS which can cause IFCCs to occur in any shared paths. This type of case MAY be solved by offline/online physicall channel.If these are channels that you can do offline/online : From all Operating systems, offline all paths,channels (SW offline) then Using HMC,online these channels (HW online) and from z/OS online channels and paths.They will become online as soon as you do HW online,but as far as I remember,SW online makes some difference. Regards Meral -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Ibm Main Sent: Monday, May 30, 2011 1:17 PM To: IBM-MAIN@bama.ua.edu Subject: Re: [IBM-MAIN] INOPERATIVE PATH Hi, thanks for your anwsers. The inoperative path appeared in devices (3490) tha are physsicaly at our other site. Both sites are connected through a DWDM network with FICON cascading. Lizette: The affected CHPIDs are 06 and 96, have a closer look at the IOS450E. The DS P, shows that the path through 06 and 96 the are inoperative (). The D M=CHP(06) shows that the paths are not operational ($). We have checked close to every hardware component (fibers, SFPs,...) involved in the path to the CU, and everything seems to be working OK. My question was why can paths get inoperative without a meaningful infrastructural change. We upgrade one z10 to z196, but the IOS appeared in LPARs in the old z10, where nothing was changed. Thanks in advance. Regards, Christian. -- 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 This message and attachments are confidential and intended solely for the individual(s) stated in this message. If you received this message although you are not the addressee, you are responsible to keep the message confidential. The sender has no responsibility for the accuracy or correctness of the information in the message and its attachments. Our company shall have no liability for any changes or late receiving, loss of integrity and confidentiality, viruses and any damages caused in anyway to your computer system. Bu mesaj ve ekleri, mesajda gonderildigi belirtilen kisi/kisilere ozeldir ve gizlidir. Bu mesajin muhatabi olmamaniza ragmen tarafiniza ulasmis olmasi halinde mesaj iceriginin gizliligi ve bu gizlilik yukumlulugune uyulmasi zorunlulugu tarafiniz icin de soz konusudur. Mesaj ve eklerinde yer alan bilgilerin dogrulugu ve guncelligi konusunda gonderenin ya da sirketimizin herhangi bir sorumlulugu bulunmamaktadir. Sirketimiz mesajin ve bilgilerinin size degisiklige ugrayarak veya gec ulasmasindan, butunlugunun ve gizliliginin korunamamasindan, virus icermesinden ve bilgisayar sisteminize verebilecegi herhangi bir zarardan sorumlu tutulamaz. -- 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
George McLaren is out of the office
I will be out of the office starting 30/05/2011 and will not return until 01/06/2011. I will respond to your mail, if required ,on my return. If urgent please contact Chris McClory on 58502 -- 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: Excessive CPU usage in SDSF
On Mon, 30 May 2011 04:54:50 -0700, Schwarz, Barry A wrote: I noticed this once and when I looked at the operator he was banging the enter key to refresh the display several times a second. Easy enough to check and if so a little OJT might be all you need. There ought to be a better way. In the design of SYSLOG and SDSF, not merely operator practice. I assume the real operators console incurs no such prohibitive overhead. SDSF, likewise should have an event-driven ROLL mode, rather than clock driven. The SYSLOG driver should broadcast a signal that SDSF could monitor to trigger a refresh. As a compromise, the SYSLOG driver could maintain a record count in a common storage location. SDSF could poll this frequently at minimal resource expense, and perform the more costlly refresh only when it changes. Or keep SYSLOG in a UNIX file. Display utilities could stat() this file to determine when a refresh is needed. -- 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
CPU efficiency XCF - IXCQUERY vs IXCMSGI/IXCMSGO
Hi, I have just coded a IXCQUERY macro to retrieve information from members of a group All the members of the group will be using this macro so my question becomes is it more efficient for each member to use IXCQUERY or once one member has retrieved the data about members of the group use IXCMSGC for other members to retrieve the data Thanks -- 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: Excessive CPU usage in SDSF
Also can detune it a little with Checkpoint freq and Auto update to 3 secs. Might get you buy 'til the APAR closes. In a message dated 5/30/2011 6:55:26 A.M. Central Daylight Time, barry.a.schw...@boeing.com writes: Easy enough to check and if so a little OJT might be all you need. -- 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: Problems with TSO TEST
Regarding Skip Robinson's report that TEST *(IEFBR14) does not work: this is intentional and is documented. IKJ57005I has two forms, one of which is: MEMBER member NOT FOUND WITHIN THE STANDARD SEARCH ORDER From the book: Explanation: The specified member name was not found in the standard search order (TSOLIB (TASKLIB), STEPLIB or JOBLIB, or current LNKLST concatenation). Modules residing in the LPA or in both the LPA and a library in the standard search order are not eligible for the TEST command with the '*' operand. The second sentence of the explanation applies. (It surprised me too, and I asked the module owner without thinking to look it up.) I won't defend the wording of the message. Especially since to my thinking the standard search order includes LPA. And, more, it would have been found in the standard search order shown in the doucmentation if they had chosen to look. So the real problem is that it's found in LPA and that's the whole story. I'm not quite sure why this applies to TASKLIB/STEPLIB/JOBLIB in addition to LNKLST, but the reasoning for LNKLST is that there's no way to tell the system use the LNKLST copy if it's in LPA too, and TSO TEST cannot use the LPA copy. You can use the form of TEST that specifies the data set from which to fetch the module. Of course none of this has any bearing on the strange behavior cited in the original post of this thread. Peter Relson z/OS Core Technology Design -- 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: OpenPGP on z/OS
Shameless plug: A commercial implementation of PGP for z/OS is available through Symantec, which acquired PGP Inc last year. The z/OS version is sold through a reseller (see: http://www.sdsusa.com/pgp/). -- 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: Mainframe C Link Step Error - using pthread (POSIX)
LE pthread functions are mapped to names starting with @@PT*. You can see this by browing pthread.h and checking the #pragma map(pthread, ... ) statements. I would suggest that you are calling a pthread function that is not declared. Because you're using the pre-linker you should check to pre-linker output to see what the unresolved symbol is. Binder error messages are practically useless if you use the pre-linker. On 28/05/2011 3:00 AM, John Weber wrote: We are receiving an 8 on our linking of a C module on the mainframe (z/os 1.7) The error is: IEW2456E 9207 SYMBOL PTHREAD@ UNRESOLVED. Does a library need to be included in our link's syslib? Thank you! -- 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: My first mainframe experience
Gerhard: We had also semi looked at assembler G. We had a batch initiator set up for assembler H compiles (long story and probably only semi interesting). The people who developed this system and I am honestly not sure on how to explain it but I will try and shorten it to easy understanding (I can try and answer questions but memory and 30 years doesn't help). We had a subsidary that did market research and all these companies would send us sales data. We would Have these clerks essentially type up inquiries. The inquiries were request for reports says how well product x did in market y during certain dates. These inquieries were essentially assembler macros. They were submitted as batch compiles. The output was a load module that was at a later time used to run the inquiry (as a subtask) in a batch job. These jobs (two types) would run the inquiries and would take 6-7 days to finish. This part I am not clear on but the number of subtasks were 8-12 (I could be wrong) but you get the idea these were monstor cpu hogs and would essentially take all the cpu you could throw at them. The assembler H (and G) were the only assemblers that could handle the extreme macros that these programs were created by. We tried the XF and the subsequent and they could not come close to handling these macros. Ed From: Gerhard Postpischil gerh...@valley.net To: IBM-MAIN@bama.ua.edu Sent: Sun, May 29, 2011 4:09:26 PM Subject: Re: My first mainframe experience On 5/29/2011 4:41 PM, Ed Gould wrote: My memory is iffy here but IIRC both (three) source programs had to be babied to work in the FORTRAN G1 that we had. I think waterloo had a FORTRAN compiler but we were semi afraid that they wouldn't be to good at support. Can anyone confirm the Waterloo Fortran? At AMS we had WATFOR, and later WATFIV. I only used them for Star Trek (rarely), but we actually had customers that requested them. I thought they were true compilers, but the version extant in the file area is a (student type) batch system, though perfectly usable for compile and go jobs. Gerhard Postpischil Bradford, VT -- 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: My first mainframe experience
On 5/31/2011 1:08 AM, Ed Gould wrote: We had also semi looked at assembler G. We had a batch initiator set up for assembler H compiles (long story and probably only semi interesting). The people who developed this system and I am honestly not sure on how to explain it but I will try and shorten it to easy understanding (I can try and answer questions but memory and 30 years doesn't help). The assembler H (and G) were the only assemblers that could handle the extreme macros that these programs were created by. We tried the XF and the subsequent and they could not come close to handling these macros. We used the G assembler for programs that were laden with macros. One of my projects had more than 100 modules, each taking about 5 or so minutes to assemble with F and XF. Under G they each ran under a minute, but I did find an error. When a DC (or other) contained a text string with a doubled quote, and the first landed in column 71, ASM G would consider that the end of string, and treat the continuation card as comments. That made for problems as that program was distributed with a collection of macros resembling a stage 1, and I had to add extra checks for lengths of generated strings and finagle. Gerhard Postpischil Bradford, VT -- 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
