This is a discussion on Re: User Logging Question #2 - Hewlett Packard ; I always seem to discover the solution to the problems AFTER I have put a posting on this list. However, I will enlighten everyone as to the solution FYI purposes only. On the "ENA FETIDB FOR LOGGING" line I was ...
I always seem to discover the solution to the problems AFTER I have
put a posting on this list.
However, I will enlighten everyone as to the solution FYI purposes only.
On the "ENA FETIDB FOR LOGGING" line I was missing the password from
the previous GETLOG command which had executed successfully.
Once I had that plugged into the file for passing to the COMMAND intrinsic
everything worked just fine and all was well with the world once again
(until next time).....
On Tue, 8 Jul 2008 10:49:05 -0400, Brian Donaldson
>I am trying to set up the logging stuff in a DB within a Cobol program.
>It appears to work ok, but after it is all done I go into DBUTIL and it shows
>that the logid is not present, logging is disabled and so on....
>My Cobol program calls the COMMAND intrinsic to execute the commands
>and returns a zero error code/param indicating success. However, according to
>DBUTIL it was not successful.
>I know it is something I am not doing correctly but cannot see what.
>I am hoping one of the gurus here might be able to help me.
>AFTER DOING GETLOG=>+0000>+0000>GETLOG
>Creating FETIDB Database....
>WRITING=>CREATE FETIDB <
>WRITING=>SET FETIDB CIUPDATE=ON <
>WRITING=>SET FETIDB BTREEMODE1=ON,WILDCARD=@ <
>WRITING=>ENA FETIDB FOR LOGGING <
>WRITING=>ENA FETIDB FOR DEADLOCKDETECT <
>WRITING=>SET FETIDB LOGID=FETIDLOG <
>WRITING=>SET FETIDB MAINT=T49G920F <
>WRITING=>SET FETIDB PASSWORD 1=D4K1ZH4K <
>WRITING=>REL FETIDB <
>Setting Up FETIDB Database....
>AFTER DBUTIL COMMANDS=>+0000>+0000>RUN DBUTIL.PUB.SYS;STDIN=DBSCMA >LISTF1
>(Some of these commands executed successfully, the logging ones did not)
>Creating and Setting Up File (LOCKERD2.PUB.SYS)
>END OF PROGRAM
>HP30391C.09.05 TurboIMAGE/XL: DBUTIL (C) COPYRIGHT HEWLETT-PACKARD COMPANY
>>>SHOW FETIDB ALL
> For database FETIDB
> Maintenance word is not present.
> Access is enabled.
> Autodefer is disabled.
> Dumping is disabled.
> Rollback recovery is disabled.
> Recovery is disabled.
> ILR is disabled.
> Mustrecover is disabled.
> Logging is disabled.
> Prefetch is disabled.
> Indexing is disabled.
> HWMPUT is disabled.
> Add entry into lock table for deadlock detect is enabled.
> Restart is disabled.
> Database has never been stored.
> Database has been modified since last store date.
> Shadowing is disabled.
> Using Dependency SEMaphore(DSEM) is disabled.
> OLDINFOLIMITS is disabled.
> Session/Job name will not be copied to Userident in DBOPEN
> Subsystem access is READ/WRITE.
> CIUPDATE is on.
> Dynamic capacity expansion is used for 1 data sets.
> Database has at least one indexed data set.
> BTREEMODE1 is on, wildcard = "@".
> Logid is not present.
> XM log set : default XM user log set
> for volume set MPEXL_SYSTEM_VOLUME_SET
> XM log set type : circular
> XM log set size : 32 megabytes
> The language is 0 - NATIVE-3000.
> Locksizelevel set to 6.
> Buffer specifications:
> No other users are accessing the database.
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *