Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Suppress batchcom errors in TACL

153 views
Skip to first unread message

Manwith Noname

unread,
Jul 2, 2003, 6:03:17 AM7/2/03
to
Hi everyone,

I am writing a fairly simple TACL routine, part of it checks to see if
a job is running in batchcom before it starts, if it is it delays.
(for various reasons a WAITON won't do the trick).

If the batchcom STATUS command doesn't find the job, which is fine, it
returns an error to the screen:

2: Process terminated with fatal errors or diagnostics
Termination Info: 2099
Subsystem: TANDEM.NETBATCH.D30
BATCHCOM: 1 errors

This is not a problem but it looks messy and may mislead a user that
there is a problem.

This is the TACL command used:

BATCHCOM/OUTV RESULT^VAR/ ;STATUS JOB^NAME


I've tried various /OUT/, /TERM/ things but none seem to stop this
error appearing.

Any advice greatfully recieved.

Thanks

Manwith.

Dave Bossi

unread,
Jul 2, 2003, 8:13:59 AM7/2/03
to
Try this:

sink [BATCHCOM/OUTV RESULT^VAR/ ;STATUS JOB^NAME]

Dave

Doug Miller

unread,
Jul 2, 2003, 8:53:07 AM7/2/03
to
In article <b1f196f6.03070...@posting.google.com>, manwith...@hotmail.com (Manwith Noname) wrote:
>Hi everyone,
>
>I am writing a fairly simple TACL routine, part of it checks to see if
>a job is running in batchcom before it starts, if it is it delays.
>(for various reasons a WAITON won't do the trick).
>
>If the batchcom STATUS command doesn't find the job, which is fine, it
>returns an error to the screen:
>
>2: Process terminated with fatal errors or diagnostics
>Termination Info: 2099
>Subsystem: TANDEM.NETBATCH.D30
>BATCHCOM: 1 errors

This will do the trick for you:

#PUSH #ROUTEPMSG
#ROUTEPMSG NORMAL ABNORMAL
BATCHCOM ...

Even though #ROUTEPMSG has been present in TACL since D38 (maybe sooner), it
was never documented AFAIK in *any* D-series TACL manual. Look in the TACL
Reference Manual in a G06 version of TIM, or in the TACL SoftDoc (FILEINFO
$*.R9205*.T9205* should locate it) for more information.


--
Regards,
Doug Miller (alphageek-at-milmac-dot-com)

Save the baby humans - stop partial-birth abortion NOW

Malc B

unread,
Jul 2, 2003, 9:40:16 AM7/2/03
to
Two suggestions

if you run your batchcom process as an INLINE process, you can use the
INLINETO command to send all the output to a variable, so you should
lose all that unwanted screen display.

Prefix the BATCHCOM ... line with the SINK statement which will
discard the output; OK if you don't want to reference anything later
on.

Doug Miller

unread,
Jul 2, 2003, 11:41:15 AM7/2/03
to
In article <adb0e8ae.03070...@posting.google.com>, Mal...@mbehenna.freeserve.co.uk (Malc B) wrote:
>Two suggestions

Neither of which works...

>
>if you run your batchcom process as an INLINE process, you can use the
>INLINETO command to send all the output to a variable, so you should
>lose all that unwanted screen display.

This will redirect Batchcom's output...


>
>Prefix the BATCHCOM ... line with the SINK statement which will
>discard the output; OK if you don't want to reference anything later
>on.

.. and this will suppress it.

However, the messages are coming from TACL, not from Batchcom, so neither
method has any effect.

Refer to my post earlier in this thread, or do a Google search on this NG for
"#ROUTEPMSG", for the correct method of suppressing these messages.

QjoeW.Ep...@tmindspring.ycom

unread,
Jul 2, 2003, 9:52:37 PM7/2/03
to
Doug's solution (like most of them) is a good one. I use this
technique all the time.

On Wed, 02 Jul 2003 12:53:07 GMT, spam...@milmac.com (Doug Miller)
spewed forth:

>In article <b1f196f6.03070...@posting.google.com>, manwith...@hotmail.com (Manwith Noname) wrote:
>>Hi everyone,
>>
>>I am writing a fairly simple TACL routine, part of it checks to see if
>>a job is running in batchcom before it starts, if it is it delays.
>>(for various reasons a WAITON won't do the trick).
>>
>>If the batchcom STATUS command doesn't find the job, which is fine, it
>>returns an error to the screen:
>>
>>2: Process terminated with fatal errors or diagnostics
>>Termination Info: 2099
>>Subsystem: TANDEM.NETBATCH.D30
>>BATCHCOM: 1 errors
>
>This will do the trick for you:
>
>#PUSH #ROUTEPMSG
>#ROUTEPMSG NORMAL ABNORMAL
>BATCHCOM ...
>
>Even though #ROUTEPMSG has been present in TACL since D38 (maybe sooner), it
>was never documented AFAIK in *any* D-series TACL manual. Look in the TACL
>Reference Manual in a G06 version of TIM, or in the TACL SoftDoc (FILEINFO
>$*.R9205*.T9205* should locate it) for more information.

```
Joe
(remove "q.w.e.r.t.y" to reply by email)

michael sage

unread,
Jul 3, 2003, 8:51:16 AM7/3/03
to
> Even though #ROUTEPMSG has been present in TACL since D38 (maybe sooner), it
> was never documented AFAIK in *any* D-series TACL manual. Look in the TACL
> Reference Manual in a G06 version of TIM, or in the TACL SoftDoc (FILEINFO
> $*.R9205*.T9205* should locate it) for more information.

It's definitely in the TACL manual on the G06.16 CD.

0 new messages