RE: [U2] [UD] problem calling program from shell script
Thank you to those who proposed ideas. The issue appears to be something in the vendor code over which I have no control. Working with vendor now. Brad U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. - --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] problem calling program from shell script
In the UniData Command Reference you will find the following under PHANTOM. @USER.TYPE returns the type of process currently running. There are three types of processes: - Normal terminal processes (@USER.TYPE = 0). - Background (PHANTOM) processes (@USER.TYPE = 1). - Redirected standard input (@USER.TYPE = 2). Kathleene M Hunter Resolution Provider -Original Message- From: Kevin King [mailto:[EMAIL PROTECTED] Sent: Saturday, January 26, 2008 7:49 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UD] problem calling program from shell script @USER.TYPE = 2 is new to me. The documentation describes it as Redirected Standard Input which makes me think that yes, that could definitely change the mechanics of starting a phantom. On Jan 25, 2008 11:00 AM, [EMAIL PROTECTED] wrote: How is MT.PROC starting MT.WATCH? I wish I knew. That's part of my problem since both MT.PROC and MT.WATCH are 3rd party software. One more clue that may make your question irrelevant: in a successful, non-scripted run, the phantoms start up before MT.WATCH starts displaying status. This might mean that the issue lies in MT.PROC instead. I've started looking at @USER.TYPE. Is there any UniData reason @USER.TYPE = 2 would cause a phantom not to start? My tests suggest No, but would like confirmation. Brad U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. - --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- -Kevin http://www.PrecisOnline.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UD] problem calling program from shell script
@USER.TYPE = 2 is new to me. The documentation describes it as Redirected Standard Input which makes me think that yes, that could definitely change the mechanics of starting a phantom. On Jan 25, 2008 11:00 AM, [EMAIL PROTECTED] wrote: How is MT.PROC starting MT.WATCH? I wish I knew. That's part of my problem since both MT.PROC and MT.WATCH are 3rd party software. One more clue that may make your question irrelevant: in a successful, non-scripted run, the phantoms start up before MT.WATCH starts displaying status. This might mean that the issue lies in MT.PROC instead. I've started looking at @USER.TYPE. Is there any UniData reason @USER.TYPE = 2 would cause a phantom not to start? My tests suggest No, but would like confirmation. Brad U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. - --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- -Kevin http://www.PrecisOnline.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UD] problem calling program from shell script
How is MT.PROC starting MT.WATCH? --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UD] problem calling program from shell script
How is MT.PROC starting MT.WATCH? I wish I knew. That's part of my problem since both MT.PROC and MT.WATCH are 3rd party software. One more clue that may make your question irrelevant: in a successful, non-scripted run, the phantoms start up before MT.WATCH starts displaying status. This might mean that the issue lies in MT.PROC instead. I've started looking at @USER.TYPE. Is there any UniData reason @USER.TYPE = 2 would cause a phantom not to start? My tests suggest No, but would like confirmation. Brad U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. - --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
