I can't say explain why it **ever** worked with 31:00. The DELAY stage syntax
shows arguments of:
>>- + --+------------------+--ss--><
+--+-------+--mm:--+
+--hh:--+
The above (with NO imbedded space) being for a time **relative** to the
**current** time (the purpose of the leading '+').
E.g.
PIPE LITERAL +31:00:00 | DELAY
would delay for 31 hours from the current time.
and, for a specific time of day (as opposed to a relative time from the current
time), then ...
>>-hh--+---------------------+--><
+--:mm--+--+-------+--+
+--:ss--+
"31:00" O'clock is not a valid time of day.
It is possible that in some cases you were expecting something other than
"31:00" and that number was less than or equal to "24:00:00"? The "07:00"
should work as you expect, delaying util the next "07:00" time of day. But
perhaps if you want to delay more than 24:00:00, you want to specify that delay
as "+31:00:00".
Mike Walter
Aon Corporation
The opinions expressed herein are mine alone, not my employer's.
-----Original Message-----
From: CMSTSO Pipelines Discussion List [mailto:[email protected]] On
Behalf Of Paul Gilmartin
Sent: Tuesday, January 08, 2013 1:57 AM
To: [email protected]
Subject: Re: PIPDEL400E Delay 31:00 is not acceptable.
On Oct 6, 2011, at 16:35, Paul Gilmartin wrote:
> I have a stage that I want to perform a task daily at 07:00.
> It's mostly procedural code (mea culpa; I'm not good enough
> at pipethink). It runs flawlessly for several days, then
> sporadically crashes; all I have is a Rexx trace:
>
> PIPDEL400E Delay 31:00 is not acceptable.
> PIPMSG003I ... Issued from stage 2 of pipeline 1.
> PIPMSG001I ... Running "delay".
> 27 *-* 'callpipe literal' When '| delay | var stopped'
> +++ RC(400) +++
> messg 00000001SMTP * From SMTP: Received Spool File 7193
> messg 00000001SMTP * From SMTP: Mail delivered to: ...
>
> Why is Delay 31:00 suddenly unacceptable when it worked for
> the previous five (according to the log) days? Is there
> a good way to diagnose this?
>
> pipe query
> PIPINX086I CMS/TSO Pipelines, 5654-030/5655-A17 1.0112 (Version.Release/Mod)
> - Generated 6 Jun 2011 at 08:31:39.
>
This persisted for a long time, intermittently. Then I noticed
other commands were failing on storage exhausted. I had admin
increase VM size. Since then, the failure has not occurred.
But it would be nice if whatever component encountered the storage
shortage (if that's what it was) reported it clearly.
-- gil
