- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: PCA problem after upgrade to VMS 8.3 Alpha
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2007 04:59 AM
тАО07-05-2007 04:59 AM
PCA stopped working after I upgraded a system from VMS 7.3-2 to 8.3. I haven't reinstalled PCA and I couldn't find anything in the release notes.
The error message is:
CLCC1> run pca$primes
%DEBUG-F-CANTGETMAINFID, cannot get file-id for the main image file opened on ch
annel 144
-SYSTEM-F-NOPRIV, insufficient privilege or object protection violation
CLCC1> Exit
Please see the attached text file for detailed information.
I did some test runs with SET WATCH and SET AUDIT turned on (see log) and it seems when I define LIB$DEBUG PCA$COLLECTOR a bunch of DECwindows accesses are added. The problem might be in DECWindows but that may be a red herring.
TIA for any assistance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2007 06:01 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2007 06:08 AM
тАО07-05-2007 06:08 AM
Re: PCA problem after upgrade to VMS 8.3 Alpha
Sorry, no knowledge of PCA.
But I _DID_ notice
>>>
$1$DGA20:[VMS$COMMON.CRON.][000000]MYCRON.EXE_ALPHA;2
<<<
which implies that (probably during the installation of CRON) somehow a 000000.DIR was created in SYS$SYSDEVICE:[VMS$COMMON.CRON]
most common cause:
$ SET DEF
and then some incarnation fo
$ CREA/DIR [.xxx]
instead of
$ CREA/DIR [xxx]
it may or may not have to do with your problems, but I have come across some strange effects of the construct (and especially after restored BACKUPs!).
Whether or not it is your current issue, I advise you to repair it at the earliest convenient opportunity.
fwiw
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2007 07:18 AM
тАО07-05-2007 07:18 AM
Re: PCA problem after upgrade to VMS 8.3 Alpha
>>>
But I _DID_ notice
$1$DGA20:[VMS$COMMON.CRON.][000000]MYCRON.EXE_ALPHA;2
which implies that (probably during the installation of CRON) somehow a 000000.DIR was created in SYS$SYSDEVICE:[VMS$COMMON.CRON]
<<<
Couldn't it just be accessing CRON_ROOT:[000000]MYCRON.EXE_ALPHA with a rooted logical name CRON_ROOT?
cu,
Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2007 07:24 AM
тАО07-05-2007 07:24 AM
Re: PCA problem after upgrade to VMS 8.3 Alpha
The PCA version is old (4.7) and I'm also inclined not to re-install the installed version, but to upgrade to the latest versions of DECset. I need to get approvals to do that though (in progress).
I'm also not entirely convinced this is a PCA problem. There are a bunch of inter-dependencies here (Debug, PCA, DECwindows, etc.) The AUDIT alarms seem to indicate a whole bunch of DECwindows files were being accessed right before the error happened. I will do the same run (with the SET WATCH and AUDIT alarms turned on) on a working VMS 7.3-2 system so I can get a comparison on the files being accessed. I'm waiting for nighttime when the developers are gone so I get a lot less extraneous alarms.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2007 08:07 AM
тАО07-05-2007 08:07 AM
Re: PCA problem after upgrade to VMS 8.3 Alpha
o ID:227 - PCA failed to operate on OpenVMS Alpha Version
8.2.
This problem has been corrected.
So, it would be reasonable to assume that the same problem would exist on 8.3. IтАЩll have to upgrade to the latest version.