Re: EXTRACT,QEDIT macro
In caarmm9tpp6lmqp-gyutyyvt7pyiqkfgws3ycuglm7zdmy9q...@mail.gmail.com, on 04/23/2012 at 06:25 PM, Tony Harminc t...@harminc.net said: I believe you asked and received answers to the same question on Feb 10 of this year. To repeat, there is only one CIB and communications ECB per address space, There's one CSCB amd one comm ECB per job, but there may be multiple CIB's queued to the CSCB. For a batch job the Initiator has its own CSCB, making two for the address space. -- 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: INFO IBM-MAIN
Re: EXTRACT,QEDIT macro
In 006301cd2198$556b3f90$0041beb0$@net, on 04/23/2012 at 05:30 PM, Micheal Butz michealb...@optonline.net said: I have started task looking to process a Flush Or Modify command There is no FLUSH command. What you should see are START MODIFY STOP Note that some tasks, e.g., VTAM, will also see HALT, but AFAIK there's no way to DIRECT halt to an arbitrary address space. the pointer to the CIB is just for the current task No, it's for the entire job-step. I attach 4 subtasks are the com/cib address obtaining by the originating tasks valid for the subtask that I have now attached Yes, but you're responsible for synchronizing access. -- 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: INFO IBM-MAIN
Re: EXTRACT,QEDIT macro
On 25 April 2012 19:13, Shmuel Metz (Seymour J.) shmuel+ibm-m...@patriot.net wrote: on 04/23/2012 at 06:25 PM, Tony Harminc t...@harminc.net said: I believe you asked and received answers to the same question on Feb 10 of this year. To repeat, there is only one CIB and communications ECB per address space, There's one CSCB amd one comm ECB per job, but there may be multiple CIB's queued to the CSCB. For a batch job the Initiator has its own CSCB, making two for the address space. You are right, of course; I wrote CIB where I meant CSCB. The most important part of the point is that there is but one comm ECB, and like any other, it can have only one WAIT outstanding at a time. Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: EXTRACT,QEDIT macro
Thank you -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Tony Harminc Sent: Monday, April 23, 2012 6:25 PM To: IBM-MAIN@bama.ua.edu Subject: Re: EXTRACT,QEDIT macro On 23 April 2012 17:30, Micheal Butz michealb...@optonline.net wrote: I have a question regarding the usage of the Extract Qedit macros for operator communication I have started task looking to process a Flush Or Modify command via the com/cib the pointer to the CIB is just for the current task If after issuing the EXTRACT to get the address of the communication parameter list (com) and the communication input buffer (cib) I attach 4 subtasks are the com/cib address obtaining by the originating tasks valid for the subtask that I have now attached I believe you asked and received answers to the same question on Feb 10 of this year. To repeat, there is only one CIB and communications ECB per address space, and any task can wait on it (there is special code to allow this without running onto the key mismatch problems you have encountered with other ECBs). But you still cannot wait more than once at a time on a single ECB, so you must coordinate that somehow. Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: EXTRACT,QEDIT macro
Thank you -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Gerhard Postpischil Sent: Monday, April 23, 2012 8:49 PM To: IBM-MAIN@bama.ua.edu Subject: Re: EXTRACT,QEDIT macro On 4/23/2012 5:30 PM, Micheal Butz wrote: If after issuing the EXTRACT to get the address of the communication parameter list (com) and the communication input buffer (cib) I attach 4 subtasks are the com/cib address obtaining by the originating tasks valid for the subtask that I have now attached The CIB is one element in a chain of 0 to a maximum count, depending on how you initialized processing. I usually set the maximum to 1 because that makes the logic a little simpler. When your program starts, there may or may not be a START CIB. You should see one in an STC, but not usually when running under an initiator. After you set the maximum CIB count to non-zero, the CommECB is posted when a STOP or MODify adds a CIB to the chain. After you process that CIB, you would normally free it. Once you understand the processing, the QEDIT description should make more sense. Also note that a STOP command posts the ECB with an X'50', whereas all others post with X'40'. Gerhard Postpischil Bradford, VT -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
EXTRACT,QEDIT macro
Hi, I have a question regarding the usage of the Extract Qedit macros for operator communication I have started task looking to process a Flush Or Modify command via the com/cib the pointer to the CIB is just for the current task If after issuing the EXTRACT to get the address of the communication parameter list (com) and the communication input buffer (cib) I attach 4 subtasks are the com/cib address obtaining by the originating tasks valid for the subtask that I have now attached Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: EXTRACT,QEDIT macro
You can process a stop (P) or modify (F) command. The CIB is the CIB is the CIB no matter how many tasks you have. Only one can wait on the (on any, for that matter) ECB at one time, however. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Micheal Butz Sent: Monday, April 23, 2012 2:31 PM To: IBM-MAIN@bama.ua.edu Subject: EXTRACT,QEDIT macro Hi, I have a question regarding the usage of the Extract Qedit macros for operator communication I have started task looking to process a Flush Or Modify command via the com/cib the pointer to the CIB is just for the current task If after issuing the EXTRACT to get the address of the communication parameter list (com) and the communication input buffer (cib) I attach 4 subtasks are the com/cib address obtaining by the originating tasks valid for the subtask that I have now attached -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: EXTRACT,QEDIT macro
On 23 April 2012 17:30, Micheal Butz michealb...@optonline.net wrote: I have a question regarding the usage of the Extract Qedit macros for operator communication I have started task looking to process a Flush Or Modify command via the com/cib the pointer to the CIB is just for the current task If after issuing the EXTRACT to get the address of the communication parameter list (com) and the communication input buffer (cib) I attach 4 subtasks are the com/cib address obtaining by the originating tasks valid for the subtask that I have now attached I believe you asked and received answers to the same question on Feb 10 of this year. To repeat, there is only one CIB and communications ECB per address space, and any task can wait on it (there is special code to allow this without running onto the key mismatch problems you have encountered with other ECBs). But you still cannot wait more than once at a time on a single ECB, so you must coordinate that somehow. Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: EXTRACT,QEDIT macro
On 4/23/2012 5:30 PM, Micheal Butz wrote: If after issuing the EXTRACT to get the address of the communication parameter list (com) and the communication input buffer (cib) I attach 4 subtasks are the com/cib address obtaining by the originating tasks valid for the subtask that I have now attached The CIB is one element in a chain of 0 to a maximum count, depending on how you initialized processing. I usually set the maximum to 1 because that makes the logic a little simpler. When your program starts, there may or may not be a START CIB. You should see one in an STC, but not usually when running under an initiator. After you set the maximum CIB count to non-zero, the CommECB is posted when a STOP or MODify adds a CIB to the chain. After you process that CIB, you would normally free it. Once you understand the processing, the QEDIT description should make more sense. Also note that a STOP command posts the ECB with an X'50', whereas all others post with X'40'. Gerhard Postpischil Bradford, VT -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
