Thank you, it seems to do just what I need.

-----Original Message-----
From: Ray Overby [mailto:snip] 
Sent: Friday, July 11, 2008 12:42 PM
To: [email protected]
Subject: Re: Passing data within the ISPF Data Set List Filter Exit

Barry,

The non-auth name/token services comes to mind.

Ray Overby



Schwarz, Barry A wrote:
> When using ISPF 3.4 on a system with HSM, the migrated datasets show 
> up with a volser of MIGRATn.  Most of the time, the user is only 
> interested in the active datasets (which frequently are in the 
> minority).  I can use the filter exit to suppress the migrated
entries.
>
> I'm trying to find a way to handle the unusual request and allow the 
> user to specify that he wants the migrated ones also.  I thought of 
> specifying MIGRAT in the volser field and let the exit update it 
> during the first call.  Unfortunately, the exit has no built-in way to

> communicate with itself on the next call.  Is there some field 
> available to the exit (non-APF) that can be used to pass information 
> from the first call (when it process panel data) to subsequent calls 
> (when it processes DSNs)?  Alternately, is there something I could do 
> in a REXX, for example that would leave a bread crumb the exit could
evaluate?
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO 
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>
>
>   

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search
the archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to