Clarification required for ISFCALLS



IBM's Command List programming language & Restructured Extended Executor

Re: Clarification required for ISFCALLS

Postby BillyBoyo » Sat Apr 21, 2012 2:56 am

BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: Re: Clarification required for ISFCALLS

 

Re: Clarification required for ISFCALLS

Postby Viswanathchandru » Sun Apr 29, 2012 1:59 pm

Hello Bill, Thanks for the time!

Yes, I do tried that one also. But i can't get the required output or expected one. It again shows the current day. Here is the snipet. Also, if i use these special variables i'm getting RC=4 from the READ SYSLOG. Not sure whether i miss something. Can anyone guide me..

Here is the code with special variable declaration part.
/* REXX */                                               
TRACE ?I                                                 
THISDAY = DATE("S")                                       
THISDAY = THISDAY - 1                                     
ISFSTARTDATE = DATE("U",THISDAY,"S")                     
ISFSTOPDATE = DATE("U",THISDAY,"S")                       
RC_ISF = ISFCALLS("ON")                                   
ISFLINELIM = 100                                         
ADDRESS TSO                                               
 "ALLOC DA('SYS3VCT.LOG(LOGIN1)') F(ISFIN) SHR REU"       
  "ALLOC DA('SYS3VCT.LOG(LOGOUT1)') F(ISFOUT) SHR REU"   
ADDRESS SDSF "ISFLOG READ TYPE(SYSLOG)"                   
SAY RC     


Regards,
Viswa
Viswanathchandru
 
Posts: 271
Joined: Mon Oct 25, 2010 2:24 pm
Has thanked: 25 times
Been thanked: 0 time

Re: Clarification required for ISFCALLS

Postby BillyBoyo » Sun Apr 29, 2012 4:23 pm

What did the trace show?

Did you try the IBM example, and what did that give you?

Why didn't you include the time?

Did you find out what the RC=4 might mean?
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: Clarification required for ISFCALLS

Postby Viswanathchandru » Wed May 02, 2012 10:43 pm

Hello Bill, Thanks and sorry for the delayed response.

What did the trace show?
I'm not able to get any specific errors but i can get a message like the script is processing with the supplied inputs. i.e with the dates specified.

Did you try the IBM example, and what did that give you?
yes, I tried but i faced some error very similar to this.

Why didn't you include the time
. Apologize i believe the default will gather the entire 24 hrs as per the document. so thought not necessary :(

Did you find out what the RC=4 might mean?
Browsed the manual for ISFLOG return codes and it says that all the expected functions may not be completed. Please guide me through this. Apologize if i or my thoughts are wrong!

Regards,
Viswa
Viswanathchandru
 
Posts: 271
Joined: Mon Oct 25, 2010 2:24 pm
Has thanked: 25 times
Been thanked: 0 time

Re: Clarification required for ISFCALLS

Postby Pedro » Thu May 03, 2012 2:27 am

I do not see where you are checking the response. "ISFLOG READ TYPE(SYSLOG)" will put output into the ISFLINES. stem variable, as documented in the manual.

This worked for me (more or less):
/* REXX */                                     
TRACE('r')                                     
THISDAY = DATE("S")                             
THISDAY = THISDAY - 1                           
ISFSTARTDATE = DATE("U",THISDAY,"S")           
ISFSTOPDATE = DATE("U",THISDAY,"S")             
Say 'start ('ISFSTARTDATE') stop('ISFSTopDATE')'
RC_ISF = ISFCALLS("ON")                         
ISFLINELIM = 100                               
ADDRESS SDSF "ISFLOG READ TYPE(SYSLOG)"         
SAY RC                                         
Say 'isfline.0' isfline.0                       
Do ix = 1 to isfline.0                         
 Say 'isfline.'ix left(isfline.ix,80)           
End                                             
Pedro Vera
User avatar
Pedro
 
Posts: 569
Joined: Thu Jul 31, 2008 9:59 pm
Location: Silicon Valley
Has thanked: 0 time
Been thanked: 39 times

Re: Clarification required for ISFCALLS

Postby Viswanathchandru » Thu May 03, 2012 3:50 pm

Hello Pedro, Thanks for your time! I really cant understand where do i go wrong! Even i pasted the same code that you have posted here and that too didnt give me what is expected in accordance to the script. I added EXECIO at the last, no more modification in the codes posted here. But still i'm getting the output of the current date. i.e. 2012124(05/03) but what it should give is 2012123(05/03) according to the script. If possible could you please post/tell me the output date that you got from this code. Also, again i'm getting RC 4 from the ISFLOG step. browsed the manual and it says " all the functions can't be completed" . Does this means the ISFSTARTDATE special variable will not work? confused. Can anyone guide me in understanding this? Please let me know if i need to furnish any more information on this. Apologize if i or my thoughts are wrong!


Regards,
Viswa
Viswanathchandru
 
Posts: 271
Joined: Mon Oct 25, 2010 2:24 pm
Has thanked: 25 times
Been thanked: 0 time

Re: Clarification required for ISFCALLS

Postby Pedro » Thu May 03, 2012 11:12 pm

as documented in the manual.


The devil is in the details... I was curious about your sample program, so I copied it without verifying the details. And it sort of worked.

But when the details are questioned, then it becomes clear what was wrong. You did not copy the IBM example faithfully. You are using the wrong control variables. See the section 'Special variables for use with the ISFLOG command" in "SDSF Operation and Customization", SA22-7670-15, which can be found here: http://www-03.ibm.com/systems/z/os/zos/bkserv/r13pdf/
Pedro Vera
User avatar
Pedro
 
Posts: 569
Joined: Thu Jul 31, 2008 9:59 pm
Location: Silicon Valley
Has thanked: 0 time
Been thanked: 39 times

Previous

Return to CLIST & REXX

 


  • Related topics
    Replies
    Views
    Last post