If optional bit 240 is set and a batch program binds to a CV with a DBNAME which will re-route the transaction to another CV, then the TASK-CODE field in PMARPT01 will be low-values.
CA-IDMS all supported releases.
This is to be expected.
If optional bit 240 is not set, then the TASK-CODE field is set to the name of the program load-module regardless of whether the transaction is re-routed to another CV or not.
If optional bit 240 is set, then for a normal transaction running in the same CV, TASK-CODE will be the value assigned to PROGRAM-NAME in the program code at the time of the BIND RUNUNIT.
For a transaction routed to a back-end CV, TASK-CODE will be RHDCNP3S on the back-end, and low-values on the front-end CV.
This is normal behaviour. The task on the front-end has little meaning and is simply a "stub" task for the entry of the program to the IDMS environment.