[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DEC/EDI |
| Notice: | DEC/EDI V2.1 - see note 2002 |
| Moderator: | METSYS::BABER |
|
| Created: | Wed Jun 06 1990 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3150 |
| Total number of notes: | 13466 |
3084.0. "decdtm system service call error..." by KERNEL::SIMPSONR (fred) Wed Apr 02 1997 19:41
VMS V6.1 DECedi V2.1c
This problem refers to the same enviroment as Note Number: 3083. When they
perform a track call to fetch the stuck documents it has failed just the once
due to a server error.They look in the decedi error log and they find:
RDB-F-SYS_REQUEST_CAL, error from system services request called from 113
RDB-E-DECDTMERR, decdtm system service call error
SYSTEM-F-NOLOG, trasaction log not found
Noname-i-nomsg 03d9dd63
Noname-i-nomsg 03d9af93
This caused their Cobol program using the C interface to terminate. But they
were able to restart it. This may have happenned twice in about 40 test runs,
about 10000 documents, any ideas?
Cheers,
Richard Simpson.
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3084.1 | Distributed Transaction Monitor related problem | UTRTSC::SMEETS | Workgroup support | Wed Apr 02 1997 19:54 | 21 |
| 3084.2 | LMCP> CREATE LOG SYSTEM$UTVH07 | FLYWAY::GRIFFITHS | Andrew Griffiths @ZUO | Wed Apr 02 1997 21:02 | 19 |
| I also had this problem some tiome ago.
I solved this by recreating the DTM transaction file using
LMCP as follows :-
e.g. on node UTVH07
SYSTEM UTVH07: MCR LMCP
Log Manager Control Program V1.1
LMCP> show log
%RMS-E-FNF, file not found
LMCP> CREATE LOG SYSTEM$UTVH07
Transaction log SYS$COMMON:[SYSEXE]SYSTEM$UTVH07.LM$JOURNAL;1 created.
regards
andrew
|