The number and content of generated extents for a particular device entity varies from one function type to another. Prior to Release 6.1, separate device user source functions were required to produce a similar change to functions of different types.
To resolve this problem and expand the power of device user source, the generators insert an identifying comment before each extent that is part of a device entity that has device user source attached. The comment contains the following information: attachment level, header/footer type, program name, and function, entity, screen, format, and entity types. This comment is called the Device Source Extent Stamp (DSES) and consists of the following components.
Note: Not all extents have all components.
|
Component |
Description |
Valid Values |
|---|---|---|
|
A@L:n |
Attachment level; read as Attached at Level: |
E (entry), F (format), S (screen), R (report), and D (device) |
|
HDR:nnnnn |
Header/Footer type |
POPUP, F/SCR, PRINT |
|
FUN:nnnnnnnnnn |
Program name |
For example, UUABEFR |
|
TYPE:nnnnnnn |
Function type |
EDTRCD, DSPTRN, PRTFIL, etc. |
|
SCR#:n RPT# :n |
Screen/Report number |
1, 2, 3,4 |
|
FMT:nnn |
Format type |
RCD, CTL, HDR, FTR, etc. |
|
ENT:n |
Entity type |
F (field description) 1, 2, 3, L, R (column headers) Special field values: P (program name), ! (screen title, $ (selection text), # (command key text) |
By specifying values contained in the DSES on a SCAN command, you can conditionally test whether or not the processed extent should be modified. For example, to attach user source to a field description rather than to a field column header, scan for ‘ENT:F’ rather than ‘ENT:1’ or ‘ENT:L’.
Note: DSES is always the first line in any extent. To ensure that the current line is positioned at the DSES, include a POSITION TO=FIRST command in the user source.
The DSES is not protected from change, so be careful not to modify it accidentally.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |