From: John P. Hartmann. JOHN at EMEAVM1
RE: Structue definitions (was: 1.1.11/0016 is available for download.)
Note that Rob's example uses callpipe so that the structure definition
is complete before the next callpipe. If you have a structure that
you wish to refer to repeatedly in several PIPE commands, it may be
better to make it "globally" visible:
pipe < my structs|structure add thread
(Globally on CMS is for all intents and purposes thread scope.) Do
not attempt to define a structure in the same pipeline where you use
it unless you understand the implications of the definition being read
from an input stream.
When you are done with all the structs you can drop them by
]untested(:
pipe < my structs|deblock linend :|substr w1|struct delete thread
You can see a single structure or a number of them by
pipe struct list <names>...
Or a variation of the delete theme above. There is currently (but no
doubt that will change) a way to list all structures currently active.
>>> '| locate substr member mr.mrhdrdm of 11-* x06',
This might also be expressed as:
'| locate qualify mr 11 member mrhdrdm x06',
Which you chose is clearly a matter of taste.
I also found that when I generate structure definitions from assembler
code, I have been sloppy and used D where I should have said FL8. I
also have D areas that are really A(base),F'length'. Such things will
need manual tuning.
It should be fairly easy to write converters for C and COBOL, and a
subset of PL/I, but I haven't had the need to make one yet.
j. [EMAIL PROTECTED]
