Recover RPG entry programs and concurrent cycle returns #818
Loading…
Reference in a new issue
No description provided.
Delete branch "rpg-thread-entry-recovery"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Recover RPG entry programs and concurrent cycle returns
Entry parameters and assignments
The emitter reads a fixed character copy between two entry parameters. It
also reads a literal followed by an entry parameter when the compiler
copies their combined width and pads the result with blanks. Both forms
require the complete copy operation and independent declarations for the
two parameters. A read-only parameter can only supply the value.
The module's retained PCML records supply the parameter names, input usage
and version. The emitter accepts flat PCML 7 and 8 interfaces with fixed
character and packed decimal parameters. It checks every parameter against
the recovered procedure before using any of the names. Both public noxDB
listings now contain the complete three-statement body.
Date, decimal and copyright controls
The module's named format record supplies the date order and separator.
For a nondefault comma it also distinguishes the compiler setting from
executed program text. The spelling comes from a single unused source
literal for comma or zero-comma. Conflicting spellings remain unresolved.
A copyright requires the program's length, padding and footer plus the
same text in the module's RPG constants. Long control lines break between
keywords to fit the source member.
Object comparison
The comparator includes the full retained interface and its CCSID in the
attribute comparison. Changing only the spelling or case of a retained
parameter changes those attributes. The comparator also recognizes the
compile timestamp for the measured MDY and YMD date forms with slash and
period separators. The date options themselves remain structural.
Concurrent program return
A concurrent module installs eight addresses into its run-time frames.
Sourcerer checks the entry label, every address and store, the thread-local
areas and pointer type, and the indirect return through the control slot.
The cycle reader can then distinguish this routine from the initialization
of the program's own data and retain its checks on both routines.
Two authored concurrent programs carry the routine in both saved forms.
The single-thread version of the same program omits it. The final return
of the public ileastic program now emits.
Gate
47152e7cd5toc8d454a4f3c8d454a4f32a3c41f8f22a3c41f8f2dd7c9e2413