HP3000-L Archives

June 1998, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Michael Berkowitz <[log in to unmask]>
Reply To:
Michael Berkowitz <[log in to unmask]>
Date:
Fri, 12 Jun 1998 10:48:47 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Gilles Schipper writes:

>>> Gilles Schipper <[log in to unmask]> 06/12/98 07:24am >>>
Does the compatability mode cobolii compiler support the "$control
post85"
compiler directive in order to utilize the "move function current-date"
capability?

If so, which version of cobolii?

If not, can someone remind me of the appropriate intrinsic to call which
will return the necessary date constructs (ie yyyymmdd, etc) - and what
are
the minimum o/s requirements which include these intrinsics (eg. 5.5 +
pp4
+ or 5.5 + pp4 + additional patches) ?

Thanks in advance.
---------------------------------------------------------------------------
The COBOLII compatability compiler says that POST85 is an INVALID
SUBSYSTEM COMMAND PARAMETER, so that lets out using the COBOL
functions.  However you can still do what you want by using the
HPCIGETVAR intrinsic and getting the variables HPYYYY, HPMONTH and
HPDATE and slapping them together to get your YYYYMMDD string.  I
believe you need PP4 to get the variable HPYYYY, otherwise you'll have
to use HPYEAR, and put your own century on.  Of course if you are
actually running on an MPE/V machine, you can't use the variables and
may have to do a call to the intrinsic DATELINE and break out the pieces
you need.

Mike Berkowitz
Guess? Inc.

ATOM RSS1 RSS2