Hi Sandra,
We've done this for a while. Our method, which has worked for years (we're currently on r19) is as follows:
Find the TCE for Task 0
Field TCESTKBA in the TCE points to the beginning of the stack
Offset x'D4' in this stack (at least at r19) points to a block of addresses, each of which points to a particular message. The eighth message is the Enter Next Task Code message (half word with the message length, followed by the message).
We use this to put the Started Task name and LPAR id into the message, as we have a lot of CVs with the same System Number running on different LPARs, so it's a quick way to see you're on the IDMS system you expect.
When you go to a new release, it's just a matter of checking the offset in the stack still points to the messages, and that the 8th is still ENTC.
Iain
Original Message:
Sent: 05-04-2021 10:50 AM
From: Sandra Mabena
Subject: Displacement for CA IDMS R19.0 Factotum's message block
Hi there,
We normally customize our "Enter Next Task Code" prompt; so after upgrading to R19.0, the message displayed needs to be updated. Does anyone know what the displacement for CA IDMS R19.0 Factotum's message block is. This worked well when we used 18.5. The documentation on the customized program refers me to see WORKD dsect in RHDCMSTR (CA Support).
------------------------------
Team Leader and Senior IT Specialist
Innovation Solutions for Finance
------------------------------