| Title: | ACMS comments and questions |
| Notice: | This is not an official software support channel. Kits 5.* |
| Moderator: | CLUSTA::HALL AN |
| Created: | Mon Feb 17 1986 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4179 |
| Total number of notes: | 15091 |
We are trying to set up ACMS to run the user interface at a new location.
The .ADB file is caching correctly, but our .RLB file is not.
The logicals on the client side are:
"ACMS$ADB_CACHE" [super] = "DSA2:[ACMS_APPL.ACMS$CACHE.]"
"ACMS$RLB_CACHE" [super] = "DSA2:[ACMS_APPL.ACMS$CACHE.]"
The error in ATR on the server side shows:
************************************************************
Type : TASK Time : 24-MAR-1997 18:14:49.50
Appl : RDFS_REMOTE_APPL
Task : T91_TASK_RUN
User : AMARAVADI
ID : HITOPS::0023000E-00000001-167C27AE-009B167C-00000001
Sub : HITOPS::0023000E-00000000-167C27AE-009B167C
Text : Task canceled in Step T91_INIT_SCR in Task T91_TASK_RUN in Group RDFS_R
EMOTE_GROUP
Internal remote request/request interface/DECforms request error
Error caching request library file _SCOPE::RDFS_LIBRARY_ROOT:[LIB]REMOTE_RETDISP
SY.RLB;134
%ACMSCACHE-E-NOT_CACHED, Error while attempting to cache file
Caching attempted when direct access failed with error:
%RMS-F-DEV, error in device name or inappropriate device type for operation
************************************************************
The request library file exists on the server side and this seems to see that
okay - so we are assuming the RMS error occurs in trying to cache the file on
the client side. Is there a way to see what invalid device this is trying to
cache the file on? Since the ADB file made it over okay, and the logicals point
to the same place how can we find out what is going on?
Thanks for your help,
Leslie and Seetaram
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4133.1 | CLUSTA::HALL | Bill Hall - ACMS Engineering - ZKO2-2 | Mon Mar 24 1997 20:21 | 15 | |
The caching of the ADB and the RLB are handled by 2 different
processes. The ADB is cached by the ACC. The RLB is cached
by the agent (in this case the CP, I presume). It's the
CP that is having a problem. The file spec is sent by
the remote appl's EXC to the CP on the front end. The
CP then attempts to access the file using this file spec,
copying it the location you specified. The easiest way
to debug this is to log into the account the CP is
using and do a DIR/SIZE of the remote file spec and then
attempt to copy it to the place you specified. One of
these is likely to fail.
Bill
| |||||
| 4133.2 | Thanks | CPCOD::JOHNSON | Peace can't be founded on injustice | Tue Mar 25 1997 11:15 | 4 |
Thank you very much. That should help. Leslie | |||||