(SYSLIB) Programming Reference Manual - Public Support Login ...

ID$–Identification Line Routine
Execution date and time
ID$ uses the current date and time unless a date and time are in the ID$ packet.
(This should be the contents of R2 at load time.) Two formats are available: default is
"CCYY mmm DD ddd HHMM:SS", or optionally "YYMMDD HHMM:SS". The date
and time are separated from the last character of the creation date/time (or
description if creation date/time is excluded) by one space.
See SFDT$ routine comments for further details on the date/time formats.
The calling program can format ID$ output for 80 characters per line (demand) or 132
characters per line (batch or breakpointed-demand). If the length of the output exceeds
the maximum character length of a line, the remainder is continued on the following line.
If the creation date/time or execution date/time does not fit on one line, they are placed
entirely on the next line (there is no wraparound for date/time).
Sample displays of an ASCII string generated by ID$.
1. MASM 3R1T1 (800827 1448:46) 1983 Sep 10 Sat 1651:18
2. FURPUR 28R3 File Utility Routine/Program File Utility Routine
(820312 1356:02) 1984 May 11 Fri 1017:24
11.1. MASM Interface
The ID$ routine may be called directly from MASM programs. Subsection 11.3
describes the ID$ packet format and the MASM PROC I$DPKT that generates the
packet. Subsection 11.1.2 describes the calling sequence for ID$, the MASM PROC
I$D$ to call ID$, and the MASM PROC I$DPRINT to print the output.
11.1.1. Packet
The calling program must provide ID$ with an 11-word (or more) packet. The ID$ packet
format is described in 11.3, and the PROC to generate the ID$ packet is described
below.
The MASM PROC I$DPKT generates the packet for the ID$ routine.
Calling Format
label I$DPKT {idlen | idbuf | ‘bufname’} {hdrlen | hdrbuf | ‘string’} optbits
11–2 7833 1733–004