c	Might as well get around to testing DATE & IDATE ... (12-Feb-1999)
c
	character*9  datbuf
	character*11 datbf4
	integer*2 gtbuf(8)
c	RSX-11M+ V4.5:
c	IDATE: iyear is 0-99 if TIM set w/ 2-digit year, else 100,101, etc.
c	(i.e. correctly indicates years since 1980, 1900 through 2050 +
	call idate(iday,imonth,iyear)
	print*,'IDATE: ',iday,imonth,iyear
	call gettim(gtbuf,ids)		! this is not in OTS, so good in M+ 4.5
	print*,'GTIM:'
	print*,' Yr,  Mo,  Day, Hr,  Min, Sec, Tck, T/S; Dir. Status' 
	write (6,10) gtbuf,ids
10	format (1x,9i5.4)
c	DATE just makes GTIM$S DPB on stack, calls it & fills in string values
c	Disassembly of routine shows that datbuf fmt always dd-mmm-yy (not y4)
	call date(datbuf)	! takes only 1 arg., otherwise traps
	print*,'DATE: ',datbuf
	call date4(datbf4)
	print*,'DATE4: ',datbf4
	call exit
	end