If this is for your in-house code, why don't you simply
define your own variable and set it in a system-wide logon
UDC.  Make the addition during your 6.0 migration.  That
way it will be much more apparent in your code whether that
particular function exists then by performing an apparently
non-related LISTJOB command.

Regards,
Michael L Gueterman
Easy Does It Technologies
Allaire Alliance Partner
email: [log in to unmask]
http://www.editcorp.com
voice: (888) 858-EDIT -or- (509) 943-5108
fax:   (509) 946-1170

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Michael Berkowitz
> Sent: Monday, November 23, 1998 2:09 PM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] Am I 6.0 or not -Reply
>
>
> Wirt among others replies to my question
>
> >>> Wirt Atmar <[log in to unmask]> 11/23/98 12:31pm >>>
> Michael Berkowitz asks:
>
> > Is there a system variable on 6.0 only, that I can
> >  check for its existence with the HPCIGETVAR intrinsic, to
> say I'm on
> 6.0
> >  or not?
>
> HPVERSION works well for gross OS-level determinations -- and it's
> been in MPE
> for quite some time now.
>
> Wirt Atmar
> --------------------------------------------------------------
> -----------
> I believe everyone is missing the point of my inquiry.  I'm
> not interested in
> CI level checking, but within a program.  Second, I'm looking
> for a variable
> that I can check for the existance, or non-existance of the system
> variable with the status parameter of the HPCIGETVAR
> intrinsic.  I'm not
> interested in any actual value of the variable.  Jeff's answer of
> LISTJOBQ>$NULL comes closest and can be done by looking to see if
> CIERROR 975 is returned by the COMMAND intrinsic or not,
> indicating 6.0
> or not.  However if any one knows of a 6.0 only system
> variable, I like to
> know.
>
> Mike Berkowitz
> Guess? Inc.
>