Thanks to all who responded with some very good solutions.  I have it working 
and it sends emails when it determines a problem with one of the links.  Thanks 
again to all. 


Scott R Wandschneider

Senior Systems Programmer|| Infocrossing, a Wipro Company || 11707 Miracle 
Hills Drive, Omaha, NE, 68154-4457|| ': 402.963.8905 || Ë:847.849.7223  || :: 
[email protected] **Think Green  - Please print responsibly**


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf 
Of Kris Buelens
Sent: Monday, March 23, 2009 2:02 PM
To: [email protected]
Subject: Re: RSCS Query

This could work, if ....
WAKEUP must be started before one issues the SMSG command to RSCS.  So:
  'WAKEUP +0 (IUCVMSG'
  'CP SM RSCS QUERY ....
 do forever
    "WAKEUP +"wait "(IUCVMSG QUIET"
    ....
 end
'WAKEUP RESET'

And,     seconds1 = time(seconds)
should better be     seconds1 = time('Seconds')


2009/3/23, [email protected] <[email protected]>:
> The may be a better way, but when I did it I did it like this:
>
>  <snip>
>  "CP SMSG RSCS (ML."signature") QUERY FILES ON" printer "SHOW ID",  
> "FROMUSER FILENAME FILETYPE CLASS STATUS RECORDS RECSDONE FORM"
>  </snip>
>  ...
>  <snip>
>  /**********************************************************************/
>  /*       Receive the response from RSCS.                              */
>  
> /*********************************************************************
> */
>  wait = "00:00:25"
>  message_number = "0000"
>  do forever
>    seconds1 = time(seconds)
>    "WAKEUP +"wait "(IUCVMSG QUIET"
>    if rc = 2 | rc = 6 then leave
>    seconds2 = time(seconds)
>    new_wait = seconds2 - seconds1 + 5
>    wait = "00:00:"||right(new_wait,2,0)
>    parse pull . . . message_number message_line . m_sig mtype,
>       message_text
>    if m_sig ¬= signature then iterate
>    message_line = strip(message_line,l,0)
>    if mtype = "H1" | left(message_text,5) == " Link" then
>       message_text = delstr(message_text,1,1)
>    if message_number = "0001" then leave
>    else do
>       recs = recs + 1
>       line.recs = message_text
>    end
>  end
>  </snip>
>
>  Peter
>
>
>  -----Original Message-----
>  From: The IBM z/VM Operating System [mailto:[email protected]] 
> On Behalf Of Wandschneider, Scott
>  Sent: March 23, 2009 12:54
>  To: [email protected]
>  Subject: RSCS Query
>
>  I would like to issue an RSCS QUERY LINKS and "queue" the results so I can 
> spin through the response looking for information.  Here is a snippet from an 
> experimental REXX EXEC.  The results from the query are displayed back at my 
> terminal and the @HowMany variable is always zero.  Any ideas?
>
>  Check_Links:
>  'pipe cp smsg RSCS query links | stem @Rec. '
>  @HowMany = @Rec.0
>  Say "HowMany" @HowMany
>  Do x = 1 to @HowMany
>  .
>  .
>  .
>  End /* DO */
>
>  Scott R Wandschneider
>
>  Senior Systems Programmer|| Infocrossing, a Wipro Company || 11707 
> Miracle Hills Drive, Omaha, NE, 68154-4457|| ': 402.963.8905 || 
> Ë:847.849.7223  || :: [email protected] **Think 
> Green  - Please print responsibly**
>
>
>  Confidentiality Note: This e-mail, including any attachment to it, may 
> contain material that is confidential, proprietary, privileged and/or 
> "Protected Health Information," within the meaning of the regulations under 
> the Health Insurance Portability & Accountability Act as amended.  If it is 
> not clear that you are the intended recipient, you are hereby notified that 
> you have received this transmittal in error, and any review, dissemination, 
> distribution or copying of this e-mail, including any attachment to it, is 
> strictly prohibited. If you have received this e-mail in error, please 
> immediately return it to the sender and delete it from your system. Thank you.
>
>
>
> The information transmitted is intended only for the person or entity to 
> which it is addressed and may contain confidential and/or privileged 
> material.  Any review retransmission dissemination or other use of or taking 
> any action in reliance upon this information by persons or entities other 
> than the intended recipient or delegate is strictly prohibited.  If you 
> received this in error please contact the sender and delete the material from 
> any computer.  The integrity and security of this message cannot be 
> guaranteed on the Internet.  The sender accepts no liability for the content 
> of this e-mail or for the consequences of any actions taken on the basis of 
> information provided.  The recipient should check this e-mail and any 
> attachments for the presence of viruses.  The sender accepts no liability for 
> any damage caused by any virus transmitted by this e-mail.  This disclaimer 
> is property of the TTC and must not be altered or circumvented in any manner.
>



Confidentiality Note: This e-mail, including any attachment to it, may contain 
material that is confidential, proprietary, privileged and/or "Protected Health 
Information," within the meaning of the regulations under the Health Insurance 
Portability & Accountability Act as amended.  If it is not clear that you are 
the intended recipient, you are hereby notified that you have received this 
transmittal in error, and any review, dissemination, distribution or copying of 
this e-mail, including any attachment to it, is strictly prohibited. If you 
have received this e-mail in error, please immediately return it to the sender 
and delete it from your system. Thank you.

--
Kris Buelens,
IBM Belgium, VM customer support

Reply via email to