Forum
I never took a deeper look on DSNHDECP at binary level … until these days:
DSNHDECP is output of DB2’s "make" process and results from macro DSNHDECM, literals and parameters, which is documented in target-lib.SDSNMACS(DSNHDECM):
[tt]DSNHDECP CSECTÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
DECPIDÂ Â DCÂ Â XL2’20C0’Â Â Â Â Â Â BLOCK IDÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
DECPLENÂ DCÂ Â AL2(DECPLAST-DSNHDECP)Â LENGTH OF BLOCKÂ Â Â Â Â Â Â Â Â Â Â
DECPEYEÂ DCÂ Â CL4’DECP’Â Â Â Â Â Â EYE CATCHERÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
DECPRELÂ DCÂ Â CL4’1010’Â Â Â Â Â Â VERSION, RELEASE, MOD LEVELÂ Â Â Â Â Â Â
      DC  CL4’  ‚      RESERVED                  Â
DECPLVLÂ DCÂ Â CL8’V10R1M0 ‚Â Â Â Â MACRO CHANGE LEVELÂ Â Â Â Â Â Â Â Â Â Â Â
*Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â COORDINATE WITH DSNDDECP MACROÂ Â Â Â
[/tt]
For complete description of all elements, see DSNHDECM on SDSNMACS library.
Ciao
Gernot
PS: Zefrim, what is the result of your DSNHDECP binary analysis? What is the "plus" compared to SYSPROC.ADMIN_INFO_SYSPARM or -DISPLAY command?
