CA IDMS

Expand all | Collapse all

Displacement for CA IDMS R19.0 Factotum's message block

  • 1.  Displacement for CA IDMS R19.0 Factotum's message block

    Posted 8 days ago
    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
    ------------------------------


  • 2.  RE: Displacement for CA IDMS R19.0 Factotum's message block

    Broadcom Employee
    Posted 8 days ago
    Hi Sandra,
       The ENTER NEXT TASK CODE message is stored in the dictionary message area as DC055007.  You can modify the text of the message in the dictionary.



  • 3.  RE: Displacement for CA IDMS R19.0 Factotum's message block

    Posted 8 days ago
    Hi Brian,

    Yes, I know that.  We're customising the message using assembler and I need the displacement I mention, to get it to work correctly​

    ------------------------------
    Team Leader and Senior IT Specialist
    Innovation Solutions for Finance
    ------------------------------



  • 4.  RE: Displacement for CA IDMS R19.0 Factotum's message block

    Posted 8 days ago
    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



  • 5.  RE: Displacement for CA IDMS R19.0 Factotum's message block

    Posted 8 days ago
    Hi Ian,

    Thank you very much!  This is exactly what Ive been looking for... we use it the same way .

    ------------------------------
    Team Leader and Senior IT Specialist
    Innovation Solutions for Finance
    ------------------------------