Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

OpenVms Cobol RMS RU_Journaling enabled return-status 9332

SOLVED
Go to solution
Jesse Grijalva
Occasional Advisor

OpenVms Cobol RMS RU_Journaling enabled return-status 9332

We are in process of enabling RMS RU_journaling on certain RMS files. For Test purpose I have set RU_Journaling for one particular rms file. We have the proper RMSJNL license and have set the system logical "SYS$DECDTM_INHINIT" = "NO".
In my test cobol program, following the OPEN I-O statement I have the Call "SYS$Start_Transw" to start the transaction. I Get a faulire return status = 9332. I then executed the sample procedure and program in SYS$examples:RMSJNL_EXAMPLE.com. Same return status from "SYS$Start_Transw". Any recommendations? I cannot locate the translation to the return status. We are running Openvms 7.3-2
9 REPLIES
Jim_McKinney
Honored Contributor

Re: OpenVms Cobol RMS RU_Journaling enabled return-status 9332

$ exit 9332
%SYSTEM-F-NOLOG, transaction log not found

I presume that SYS$DECDTM_INHINIT" = "NO" is a typo and you meant inhiBit?
Jesse Grijalva
Occasional Advisor

Re: OpenVms Cobol RMS RU_Journaling enabled return-status 9332

Correct a Typo.

(LNM$SYSTEM_TABLE)

"SYS$DECDTM_INHIBIT" = "NO"
"SYS$DECDTM_NODE_ADDRESS" = "1076"
"SYS$DECDTM_NODE_NAME" = "PHXDEV"

Jur van der Burg
Respected Contributor
Solution

Re: OpenVms Cobol RMS RU_Journaling enabled return-status 9332

Deassign SYS$DECDTM_INHIBIT. If it translates to anything decdtm will not be started.

Jur.
Jesse Grijalva
Occasional Advisor

Re: OpenVms Cobol RMS RU_Journaling enabled return-status 9332

I will deass/sys SYS$DECDTM_INHIBIT.

Also the system message
$ exit 9332
%SYSTEM-F-NOLOG, transaction log not found

translates to (See attached). I'll have our Sys Admin follow up.

Thank you.
Jur van der Burg
Respected Contributor

Re: OpenVms Cobol RMS RU_Journaling enabled return-status 9332

You may also need to create a decdtm log file (mc lmcp create log system$'nodename')

Jur.
Jesse Grijalva
Occasional Advisor

Re: OpenVms Cobol RMS RU_Journaling enabled return-status 9332


We've created the journal log and continued my test. I now receive return status 9340.

$ exit 9340
%SYSTEM-F-TPDISABLED, the TP_SERVER process is not running on this node

I thought removing the SYS$DECDTM_INHIBIT logical would enable DECdtm service.

$ sh log SYS$DECDTM_INHIBIT
%SHOW-S-NOTRAN, no translation for logical name SYS$DECDTM_INHIBIT

I am researching, recommendations appreciated.
Hein van den Heuvel
Honored Contributor

Re: OpenVms Cobol RMS RU_Journaling enabled return-status 9332

That logical name is looked at during boot.
Reassigning after boot does not make it start on its own.
You will need to run:

@SYS$STARTUP:DECDTM$STARTUP.COM

http://h71000.www7.hp.com/doc/73final/6017/6017pro_104.html

Hein.
Jesse Grijalva
Occasional Advisor

Re: OpenVms Cobol RMS RU_Journaling enabled return-status 9332

Fantastic! We're off and running.

Thank you all. This a great forum.
Hein van den Heuvel
Honored Contributor

Re: OpenVms Cobol RMS RU_Journaling enabled return-status 9332

Thanks for the feedback!

Of course the real fun has only just begun.
While enabling RUJ looks, and is, easy enough to set up there are operational and performance implications.

There will be those per process .RUJ files being hammered, deferred writes will aggresively be used, aand there may be a surprise prolonged record lock holding.

Hope this helps some,
Hein van den Heuvel (at gmail dot com)
HvdH Performance Consulting

(contact me offline if you think additional, applicaction specific help is desirable)