Wed, 29 Sep 2010 09:44:19 -0700

 


----------------------------

Please bear with me. This may seem like a pointless question - just clean up the code, dummy! - but I am trying to shoot a problem at a customer site and I'd like to only ship "fixed" code once, so I would like to know whether I have found the real problem or not. (And don't blame me - I didn't write this code.) If a program specifies EZASMI TYPE=INITAPI, INITIALIZE THE TCP/IP ENVIRONMENT + ASYNC=('ECB') + APITYPE='2',... And then issues EZASMI TYPE=CONNECT and TYPE=WRITE *without* specifying an ECB, will the CONNECT and WRITE block and run synchronously, not returning until the CONNECT or WRITE is complete, or will the macros complete immediately without regard to how long the CONNECT or WRITE actually takes? Thanks much. Charles Mills ---------------



----------------------------

Please bear with me. This may seem like a pointless question - just clean up the code, dummy! - but I am trying to shoot a problem at a customer site and I'd like to only ship "fixed" code once, so I would like to know whether I have found the real problem or not. (And don't blame me - I didn't write this code.) If a program specifies EZASMI TYPE=INITAPI, INITIALIZE THE TCP/IP ENVIRONMENT + ASYNC=('ECB') + APITYPE='2',... And then issues EZASMI TYPE=CONNECT and TYPE=WRITE *without* specifying an ECB, will the CONNECT and WRITE block and run synchronously, not returning until the CONNECT or WRITE is complete, or will the macros complete immediately without regard to how long the CONNECT or WRITE actually takes? Thanks much. Charles Mills ---------------



----------------------------

It will block and run synchronously if ECB= is not specified in the CONNECT/WRITE/etc. Tony Thigpen -----Original Message ----- From: Charles Mills Sent: 09/29/2010 11:29 AM > Please bear with me. This may seem like a pointless question - just clean up > the code, dummy! - but I am trying to shoot a problem at a customer site and > I'd like to only ship "fixed" code once, so I would like to know whether I > have found the real problem or not. (And don't blame me - I didn't write > this code.) > > If a program specifies > > EZASMI TYPE=INITAPI, INITIALIZE THE TCP/IP ENVIRONMENT + > ASYNC=('ECB') + > APITYPE='2',... > > And then issues EZASMI TYPE=CONNECT and TYPE=WRITE *without* specifying an > ECB, will the CONNECT and WRITE block and run synchronously, not returning > until the CONNECT or WRITE is complete, or will the macros complete > immediately without regard to how long the CONNECT or WRITE actually takes? > > Thanks much. > > Charles Mills > ---------------







----------------------------

It will block and run synchronously if ECB= is not specified in the CONNECT/WRITE/etc. Tony Thigpen -----Original Message ----- From: Charles Mills Sent: 09/29/2010 11:29 AM > Please bear with me. This may seem like a pointless question - just clean up > the code, dummy! - but I am trying to shoot a problem at a customer site and > I'd like to only ship "fixed" code once, so I would like to know whether I > have found the real problem or not. (And don't blame me - I didn't write > this code.) > > If a program specifies > > EZASMI TYPE=INITAPI, INITIALIZE THE TCP/IP ENVIRONMENT + > ASYNC=('ECB') + > APITYPE='2',... > > And then issues EZASMI TYPE=CONNECT and TYPE=WRITE *without* specifying an > ECB, will the CONNECT and WRITE block and run synchronously, not returning > until the CONNECT or WRITE is complete, or will the macros complete > immediately without regard to how long the CONNECT or WRITE actually takes? > > Thanks much. > > Charles Mills > ---------------



----------------------------

Thanks. Charles -----Original Message----- From: a href="mailto:IBM TCP/IP List [mailto:IBMTCP-L@VM.MARIST.EDU] On Behalf Of Tony">IBM TCP/IP List [mailto:IBMTCP-L@VM.MARIST.EDU] On Behalf Of Tony/a> Thigpen Sent: Wednesday, September 29, 2010 9:09 AM To: IBMTCP-L@VM.MARIST.EDU Subject: Re: EZASMI synchronous/asynchronous behavior It will block and run synchronously if ECB= is not specified in the CONNECT/WRITE/etc. Tony Thigpen -----Original Message ----- From: Charles Mills Sent: 09/29/2010 11:29 AM > Please bear with me. This may seem like a pointless question - just clean up > the code, dummy! - but I am trying to shoot a problem at a customer site and > I'd like to only ship "fixed" code once, so I would like to know whether I > have found the real problem or not. (And don't blame me - I didn't write > this code.) > > If a program specifies > > EZASMI TYPE=INITAPI, INITIALIZE THE TCP/IP ENVIRONMENT + > ASYNC=('ECB') + > APITYPE='2',... > > And then issues EZASMI TYPE=CONNECT and TYPE=WRITE *without* specifying an > ECB, will the CONNECT and WRITE block and run synchronously, not returning > until the CONNECT or WRITE is complete, or will the macros complete > immediately without regard to how long the CONNECT or WRITE actually takes? > > Thanks much. > > Charles Mills > ---------------







----------------------------

Thanks. Charles -----Original Message----- From: a href="mailto:IBM TCP/IP List [mailto:IBMTCP-L@VM.MARIST.EDU] On Behalf Of Tony">IBM TCP/IP List [mailto:IBMTCP-L@VM.MARIST.EDU] On Behalf Of Tony/a> Thigpen Sent: Wednesday, September 29, 2010 9:09 AM To: IBMTCP-L@VM.MARIST.EDU Subject: Re: EZASMI synchronous/asynchronous behavior It will block and run synchronously if ECB= is not specified in the CONNECT/WRITE/etc. Tony Thigpen -----Original Message ----- From: Charles Mills Sent: 09/29/2010 11:29 AM > Please bear with me. This may seem like a pointless question - just clean up > the code, dummy! - but I am trying to shoot a problem at a customer site and > I'd like to only ship "fixed" code once, so I would like to know whether I > have found the real problem or not. (And don't blame me - I didn't write > this code.) > > If a program specifies > > EZASMI TYPE=INITAPI, INITIALIZE THE TCP/IP ENVIRONMENT + > ASYNC=('ECB') + > APITYPE='2',... > > And then issues EZASMI TYPE=CONNECT and TYPE=WRITE *without* specifying an > ECB, will the CONNECT and WRITE block and run synchronously, not returning > until the CONNECT or WRITE is complete, or will the macros complete > immediately without regard to how long the CONNECT or WRITE actually takes? > > Thanks much. > > Charles Mills > ---------------


S
e
n
i
o
r
T
u
b
e
.
o
r
g