question about clists

If you execute a clist containing TASKA, TASKB, and TASKC, and TASKA abends, TASKB and TASKC do not get executed. Is there any way to make the clist processing continue even if one of the tasks abends?

I'm talking about the CLIST command that you can execute at the ""enter next task code"" prompt, not any CLIST commands within a tool or application.

I can't think of any way to not stop processing the CLIST if a task abends, maybe one of gurus on the list can think of a way. But the obvious questions are:

1) Why is the task abending anyway? Can that be fixed or the program changed to not abend if invoked from CLIST and only issue a message?
2) Is order important - couldn't you put the task that is likely to abend at the end where it won't matter?

If you execute a clist containing TASKA, TASKB, and TASKC, and TASKA abends, TASKB and TASKC do not get executed. Is there any way to make the clist processing continue even if one of the tasks abends?

I'm talking about the CLIST command that you can execute at the ""enter next task code"" prompt, not any CLIST commands within a tool or application.

If you execute a clist containing TASKA, TASKB, and TASKC, and TASKA
abends, TASKB and TASKC do not get executed. Is there any way to make
the clist processing continue even if one of the tasks abends?

I'm talking about the CLIST command that you can execute at the ""enter
next task code"" prompt, not any CLIST commands within a tool or
application.

If you execute a clist containing TASKA, TASKB, and TASKC, and TASKA
abends, TASKB and TASKC do not get executed. Is there any way to make
the clist processing continue even if one of the tasks abends?

I'm talking about the CLIST command that you can execute at the ""enter
next task code"" prompt, not any CLIST commands within a tool or
application.

The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP

Normal

Normal
Re: question about clists
"Dan:

Good try. But even with nested CLISTs if the first clist blows up the CLIST processor stops.

If you execute a clist containing TASKA, TASKB, and TASKC, and TASKA
abends, TASKB and TASKC do not get executed. Is there any way to make
the clist processing continue even if one of the tasks abends?

I'm talking about the CLIST command that you can execute at the ""enter
next task code"" prompt, not any CLIST commands within a tool or
application.

If you execute a clist containing TASKA, TASKB, and TASKC, and TASKA
abends, TASKB and TASKC do not get executed. Is there any way to make
the clist processing continue even if one of the tasks abends?

I'm talking about the CLIST command that you can execute at the ""enter
next task code"" prompt, not any CLIST commands within a tool or
application.

Normal
Re: question about clists
"There is a way around this - but it depends on the purpose of the clist in =
the first place. You could, for example, run a btach UCF job which has a nu=
mber of lime mode IO tasks in the input stream. If any task fails subsequen=
t tasks will still run - as each time a task ends Enter-Next-Task-Code is p=
resented. Note - our last task is always either SIGNOFF or BYE because the =
batch UCF terminal can become disabled if it does not encounter a so long a=
nd see you later task before the end of the job stream.

If we knew how and why the CLIST was invoked in the first place there may b=
e other options available - but without more information I would not be gam=
e to suggest them ?

Gary says: Boycott Apple - the hardware company that puts software companie=
s out of business!=20
This e-mail message and any attachments are qualified as follows: Addressin=
g: If you have received this e-mail in error, please advise by reply e-mai=
l to the sender. Please also destroy the original transmission and its con=
tents. Confidentiality: This e-mail may contain confidential information w=
hich also may be legally privileged. Only the intended recipient(s) may ac=
cess, use, distribute or copy this e-mail. Individual Views: Unless otherw=
ise indicated, the views expressed are those of the sender, not Justice Tec=
hnology Services. Computer Viruses: It is the recipient's responsibility t=
o check the e-mail and any attached files for viruses.

If you execute a clist containing TASKA, TASKB, and TASKC, and TASKA abends=
, TASKB and TASKC do not get executed. Is there any way to make the clist =
processing continue even if one of the tasks abends?

I'm talking about the CLIST command that you can execute at the ""enter next=
task code"" prompt, not any CLIST commands within a tool or application.

Normal
Re: question about clists
"There is a way around this - but it depends on the purpose of the clist in the first place. You could, for example, run a btach UCF job which has a number of lime mode IO tasks in the input stream. If any task fails subsequent tasks will still run - as each time a task ends Enter-Next-Task-Code is presented. Note - our last task is always either SIGNOFF or BYE because the batch UCF terminal can become disabled if it does not encounter a so long and see you later task before the end of the job stream.

If we knew how and why the CLIST was invoked in the first place there may be other options available - but without more information I would not be game to suggest them ?

Gary says: Boycott Apple - the hardware company that puts software companies out of business!
This e-mail message and any attachments are qualified as follows: Addressing: If you have received this e-mail in error, please advise by reply e-mail to the sender. Please also destroy the original transmission and its contents. Confidentiality: This e-mail may contain confidential information which also may be legally privileged. Only the intended recipient(s) may access, use, distribute or copy this e-mail. Individual Views: Unless otherwise indicated, the views expressed are those of the sender, not Justice Technology Services. Computer Viruses: It is the recipient's responsibility to check the e-mail and any attached files for viruses.

If you execute a clist containing TASKA, TASKB, and TASKC, and TASKA abends, TASKB and TASKC do not get executed. Is there any way to make the clist processing continue even if one of the tasks abends?

I'm talking about the CLIST command that you can execute at the ""enter next task code"" prompt, not any CLIST commands within a tool or application.

Normal
Re: question about clists
"Some of you have asked for more information about what we are doing. Unfor=
tunately, we seem to have a bit of a security hole here, so I can't go into=
detail about the problem until it is fixed. This would seem to be a catch=
-22, except that someone has suggested a potential solution offline that I =
think will work for us. If that works out, I will provide the details afte=
rwards. Thanks for trying.

There is a way around this - but it depends on the purpose of the clist in =
the first place. You could, for example, run a btach UCF job which has a nu=
mber of lime mode IO tasks in the input stream. If any task fails subsequen=
t tasks will still run - as each time a task ends Enter-Next-Task-Code is p=
resented. Note - our last task is always either SIGNOFF or BYE because the =
batch UCF terminal can become disabled if it does not encounter a so long a=
nd see you later task before the end of the job stream.

If we knew how and why the CLIST was invoked in the first place there may b=
e other options available - but without more information I would not be gam=
e to suggest them ?

Normal
Re: question about clists
"Some of you have asked for more information about what we are doing. Unfortunately, we seem to have a bit of a security hole here, so I can't go into detail about the problem until it is fixed. This would seem to be a catch-22, except that someone has suggested a potential solution offline that I think will work for us. If that works out, I will provide the details afterwards. Thanks for trying.

There is a way around this - but it depends on the purpose of the clist in the first place. You could, for example, run a btach UCF job which has a number of lime mode IO tasks in the input stream. If any task fails subsequent tasks will still run - as each time a task ends Enter-Next-Task-Code is presented. Note - our last task is always either SIGNOFF or BYE because the batch UCF terminal can become disabled if it does not encounter a so long and see you later task before the end of the job stream.

If we knew how and why the CLIST was invoked in the first place there may be other options available - but without more information I would not be game to suggest them ?

In this instance all I am after is differences, often measured in nanoseco=
nds and rarely across minutes, between two times.

If I can get the time difference by simply getting successive values of FOR=
MAT=3D(DTS) and subtracting - then all is beautiful - I could use IDMSIN01 =
to give me DISPLAY values of the resultant time difference.

The main reason for asking is that this solves all of the problems with fir=
st time in one day (or year) and the second time being in another day (or y=
ear). It also means I don't have to write my own formatting in assembler - =
but that's been done before 8-)

Gary says: Grab them by their data - and their hearts and minds will follow=
!

This e-mail message and any attachments are qualified as follows: Addressin=
g: If you have received this e-mail in error, please advise by reply e-mai=
l to the sender. Please also destroy the original transmission and its con=
tents. Confidentiality: This e-mail may contain confidential information w=
hich also may be legally privileged. Only the intended recipient(s) may ac=
cess, use, distribute or copy this e-mail. Individual Views: Unless otherw=
ise indicated, the views expressed are those of the sender, not Justice Tec=
hnology Services. Computer Viruses: It is the recipient's responsibility t=
o check the e-mail and any attached files for viruses.
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP

Normal

Normal
Arithmetic on FORMAT=(DTS) date from #GETIME
"#GETIME FORMAT=(DTS) returns a 64 bit date/time stamp (same as the SQL date/time stamp) in registers 0 and 1. Does anybody know if you can perform arithmetic on, for example, successive values of a FORMAT=(DTS) date/time stamp.

In this instance all I am after is differences, often measured in nanoseconds and rarely across minutes, between two times.

If I can get the time difference by simply getting successive values of FORMAT=(DTS) and subtracting - then all is beautiful - I could use IDMSIN01 to give me DISPLAY values of the resultant time difference.

The main reason for asking is that this solves all of the problems with first time in one day (or year) and the second time being in another day (or year). It also means I don't have to write my own formatting in assembler - but that's been done before 8-)

Gary says: Grab them by their data - and their hearts and minds will follow!

This e-mail message and any attachments are qualified as follows: Addressing: If you have received this e-mail in error, please advise by reply e-mail to the sender. Please also destroy the original transmission and its contents. Confidentiality: This e-mail may contain confidential information which also may be legally privileged. Only the intended recipient(s) may access, use, distribute or copy this e-mail. Individual Views: Unless otherwise indicated, the views expressed are those of the sender, not Justice Technology Services. Computer Viruses: It is the recipient's responsibility to check the e-mail and any attached files for viruses.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP

Normal
Re: Arithmetic on FORMAT=(DTS) date from #GETIME
"For some unknown reason, a number of years ago I worked out the format of the IDMS DTS. I pulled my old notes and this is what I had found:

Bits 0-26 (27 bits) is the date. It is the number of days since 1/1/0001. E..g. 728,827 is 06/19/1996 (showing how long ago I did this :-) )

Bits 27-43 (17 bits) is the time in seconds. It is the number of seconds since midnight. E.g. 1 - 00:00:01 - 1 second after midnight. 86,399 (x'1517F') is 23:59:59 which is also the max value you'll see.

Bits 44-63 (20 bits) is a number that represents the sub second in 1/1,000,000's of a second. Max value is of course 999,999 or x'F423F'.

Unfortunately with this format you will have problems doing direct arithmetic between two values as soon as one date/time stamp is in one second the other in a different second - let along worrying about days or years.

I can't think of any way to not stop processing the CLIST if a task abends, maybe one of gurus on the list can think of a way. But the obvious questions are:

1) Why is the task abending anyway? Can that be fixed or the program changed to not abend if invoked from CLIST and only issue a message?
2) Is order important - couldn't you put the task that is likely to abend at the end where it won't matter?

I can't think of any way to not stop processing the CLIST if a task abends,=
maybe one of gurus on the list can think of a way. But the obvious questi=
ons are:

1) Why is the task abending anyway? Can that be fixed or the program chang=
ed to not abend if invoked from CLIST and only issue a message?
2) Is order important - couldn't you put the task that is likely to abend a=
t the end where it won't matter?