OSI/FTAM Programming Guide

NonStop FTAM Programming
HP NonStop OSI/FTAM Programming Guide—528612-001
3-38
Using Predefined Data Structures
36 INT ZLASTMOD;
37 INT ZLASTREADACCESS;
38 INT ZLASTATTRMOD;
39 INT ZCREATORID;
40 INT ZLASTMODID;
41 INT ZLASTREADERID;
42 INT ZLASTATTRMODID;
43 INT ZFILEAVLBLTY;
44 INT ZFILESIZE;
45 INT ZFUTUREFILESIZE;
46 INT ZACCESSCNTRL;
47 INT ZLEGALQUALIF;
48 INT ZPRIVATEUSE;
49 END;
50 END;
51 STRUCT ZCNSTRNTSETANDABSSYN = ZCNTNTSTYPE;
52 BEGIN
53 STRUCT CNSTRNTSETNAME;
54 BEGIN
55 INT ZNUM^ELEMENTS;
56 INT ZOBJ^ID[0:15];
57 END;
58 STRUCT ZASNAME;
59 BEGIN
60 INT ZNUM^ELEMENTS;
61 INT ZOBJ^ID[0:15];
62 END;
63 END;
64 END;
Note that in TAL data structures, as opposed to C data structures, substructures such
as ZDOCTYPENAME and ZFILEATTRS are defined within the main structure itself, and
not elsewhere. In lines 10 and 18 of the earlier C data structure, you can see that these
data structures are defined by other data structure identifiers,
zaps_ddl_obj_id_def and zftm_ddl_attr_names_def.
Again, suppose that you want to set up the values for a document type name and have
defined the contents-type parameter variable earlier in your program as follows:
STRUCT .EXT contents_type ( ZFTM^DDL^CNTNTS^TYPE^DEF );
Similarly, contents_type becomes the first element of this formula. For the
subsequent elements, refer to the above data structure. On line 15, you find the name