General type specifiers for definition statements

This topic provides information about the following specifier types:

Arithmetic operator types

The meaning of the various operators might not conform with your experience with other programming languages.

Operator	Comparison is true if
%	Integer division The first term is divided by the second term. Information Example 17 % 3 yields 5. Any remainder is ignored. Division by zero yields zero.
*	Multiplication Signs are handled algebraically. Information Example 5 * -3 yields -15; -5 * -3 yields 15.
+	Addition
-	Subtraction The second term is subtracted from the first term.
/	Rounded division The first term is divided by the second term and the result is rounded using the round half away from zero or commercial rounding method. Information Example 17 / 3 yields 6; -5 / 3 yields -2; ‑5 / -3 yields 2. Division by zero yields zero.
//	Modulus or remainder on division of the first term by the second term Information Example 17 // 3 yields 2, the remainder when 17 is divided by 3. If the second term is zero, the result is zero.

Comparison relationship types

Operator	Comparison is True If
=	First value is equal to second value
==	First value is equal to second value
EQ	First value is equal to second value
>	First value is greater than second value
GT	First value is greater than second value
>=	First value is greater than or equal to second value
GE	First value is greater than or equal to second value
<	First value is less than second value
LT	First value is less than second value
<=	First value is less than or equal to second value
LE	First value is less than or equal to second value
!=	First value is not equal to second value
<>	First value is not equal to second value
NE	First value is not equal to second value

Float types

float_type	Description
Short	Hexadecimal (traditional S/390) floating point number occupying 4 bytes
Long	Hexadecimal (traditional S/390) floating point number occupying 8 bytes
Ext Extended	Hexadecimal (traditional S/390) floating point number occupying 16 bytes

Integer types

A number of the format and condition specifications require the specification of an integer type or int_type. The following are the integer types:

int_type	Description
Char	A signed 8-bit integer occupying 1 byte
Double or LongLong	A signed 64-bit integer occupying 8 bytes
Full or Long	A signed 32-bit integer occupying 4 bytes
Half or Short	A signed 16-bit integer occupying 2 bytes
UChar	An unsigned 8-bit integer occupying 1 byte
UCharUChar	A pair of unsigned 8-bit integers to be formatted as mmm.nnn and occupying 2 bytes
UDouble or ULongLong	An unsigned 64-bit integer occupying 8 bytes
UFull or ULong	An unsigned 32-bit integer occupying 4 bytes
UHalf or UShort	An unsigned 16-bit integer occupying 1 byte
UInt24	An unsigned integer occupying 3 bytes
UNiblUNibl	A pair of 4-bit unsigned integers to be formatted as mm.nn and occupying 1 byte

Time types

time_type	Description
ChangeMan	Local time of day in the format used in ChangeMan events, character YYYY/MM/DD HH:MM:SS
Compuware	Time of day YYYYMMDDHHMMSS as written by BMC AMI Security Session Monitor
CompuwareMS	Time of day YYYYMMDDHHMMSSmmm as written by Compuware Abend-AID
DMicro	Duration in microseconds and occupying 4 bytes. The low-order bit represents 1/1000000 of a second or 1 microsecond
DMicro64	Duration in microseconds and occupying 8 bytes. The low-order bit represents 1/1000000 of a second or 1 microsecond
DMilli64	Duration in milliseconds and occupying 8 bytes. The low-order bit represents 1/1000 of a second or 1 millisecond
DMilliPack	Duration in packed milliseconds occupying 4 bytes mmmmmmmF
DSec100	Duration in seconds * 100 and occupying 4 bytes. The low-order bit represents 1/100 of a second or 10 milliseconds
DSec1000	Duration in seconds * 1000 and occupying 4 bytes. The low-order bit represents 1/1000 of a second or 1 millisecond
DSec1024	Duration in units of 1.024 milliseconds and occupying 4 bytes
DSec1048	Duration in units of 1.04876 seconds and occupying 4 bytes
DSec62500	Duration in seconds * 62500, sometimes phrased as units of 16 microseconds, and occupying 4 bytes
DRMF	Duration in the format of SMF7xINT as written by RMF: 4 bytes of packed time 0hhmmssF
DSTCK	Duration in z/Architecture STCK format; in other words, in units of microseconds times 4096 and occupying 8 bytes
Hex3	Date-only expressed as 3 hex (binary, really) bytes yydddd as in the JFCB date fields
IMS	IMS timestamps: packed yyyy dddF hh mm ss uuuuuu occupying 8 bytes
Jul	TOD timestamp and Julian date: packed yyyy dddF occupying 8 bytes
Juldt (SPE2101)	Timestamp consisting of time format HHMMSSTT and Julian date yyyy dddF occupying 8 bytes
LSTCK (SPE2201)	Time of day in z/Architecture STCK format, which occupies eight bytes and adjusts for the local time The STCK value is a UTC timestamp that is adjusted by the time-of-day offset of the system clock where the agent is running. The value is windowed (as IBM suggests). Values before 11-May-1971 11:56:54 are assumed to refer to times after 17-Sep-2042 23:53:46. New applications should consider using STCKE instead.
LSTCKE (SPE2201)	Time of day in z/Architecture STCKE format, which occupies 16 bytes and adjusts for the local time The STCKE value is a UTC timestamp that is adjusted by the time-of-day offset of the system clock where the agent is running. The value is windowed (as IBM suggests). Values before 11-May-1971 11:56:54 are assumed to refer to times after 17-Sep-2042 23:53:46. New applications should consider using STCKE instead.
PDate (SPE2104)	Packed date in the format YYYYMMDD and occupying 4 bytes
PTime (SPE2104)	Packed time in the format HHMMSSTc and occupying 4 bytes
RMF	Date and time in the format of SMF7xIST and SMF7xDAT as written by RMF: 4 bytes of packed time 0hhmmssF and 4 bytes of packed date 0cyydddF
SMF	Time of day in SMF format: seconds*100 and 0cyydddF packed date, local time, used by most SMF timestamps and occupying 8 bytes
SMFdate	0cyydddF with no time occupying 4 bytes
SMFdt,	0cyydddF tttttttt seconds * 100 (reversed order relative to SMF) and occupying 8 bytes
SMFUTC	Time of day in SMF format: seconds*100 and 0cyydddF packed date, UTC time, used by Telnet SNA Init and Terminate, and occupying 8 bytes
STCK	Time of day in z/Architecture STCK format, occupying 8 bytes The value is windowed (as IBM suggests). Values indicating times before 11-May-1971 11:56:54 are assumed to refer instead to times after 17-Sep-2042 23:53:46. New applications should consider using STCKE instead.
STCKE	Time of day in z/Architecture STCKE format, occupying 16 bytes Only the leftmost 64 bits are examined, yielding a resolution finer than 1 microsecond.
STCKDB2	DB2's shifted z/Architecture STCK value, occupying 8 bytes
STCKOffset (SPE2110)	Time offset to either GMT or local time in the format +/-HH:MM:SS, for example +05:00:00 or -05:00:00
STCKwLSO	Time of day in z/Architecture STCK format, occupying 8 bytes, and already adjusted for any Leap Second Offset (LSO) The value is windowed (as IBM suggests). Values indicating times before 11-May-1971 11:56:54 are assumed to refer instead to times after 17-Sep-2042 23:53:46.
TODUSED (SPE2110)	Elapsed time in the format DDDTHH:MM:SS.thmiju The placeholders in the format are defined as follows: DDD—Number of days elapsed T—Time designator HH:MM:SS—Hours:Minutes:Seconds t—One-digit tenth of a second (0 through 9) hmiju—Microseconds (00000 through 99999)
TSec100	Time of day in seconds * 100 and occupying 4 bytes The low-order bit represents 1/100 of a second or 10 milliseconds.