- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: VMS 732-UPDATE-V4 - error parsing 'BLOCK_SIZE'
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
тАО05-16-2005 09:36 PM
тАО05-16-2005 09:36 PM
- the percent done series up to 90%
- and then, 5 times:
%CLI-F-SYNTAX, error parsing 'BLOCK_SIZE'
-CLI-E-ENTNF, specified entity not found in command tables
%DCL-W-SKPDAT, image data (records not beginning with "$") ignored
(Yes, the prerequisite PCSI kit WAS already intalled).
Any ideas what this is about?
And anybody any ideas which 5 of total 31 consolidated patches are affected?
Anybody know how PCSI (PROD command) can be made more verbose?
$ PROD SHOW HIST /SINCE only shows UPDATE V4, not the separate consolidated modules successfully installed.
TIA
Proost.
Have one on me.
jpe
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2005 10:11 PM
тАО05-16-2005 10:11 PM
SolutionI think that kit includes the patch for COPY that adds the /BLOCK_SIZE qualifier. If you
redo the kit it will complete with no errors.
I encountered this when doing the COPY kit and
decided the reinstal it just to be sure.
The problem is a mismatch with the image and the
current DCLTABLES.
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2005 11:06 PM
тАО05-16-2005 11:06 PM
Re: VMS 732-UPDATE-V4 - error parsing 'BLOCK_SIZE'
Bingo!
We had already rebooted, so the new DCLTABLES were activated, and the second install had lots of Already Done (as it should), and no more BLOCK_SIZE errors.
But, what happened to the highly praised VMS Quality Assurance?
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2005 11:10 PM
тАО05-16-2005 11:10 PM
Re: VMS 732-UPDATE-V4 - error parsing 'BLOCK_SIZE'
I think it is one of the chicken'n'egg situations.
You use COPY to copy COPY.EXE, then any copies after
that use the new COPY but DCLTABLES doesn't yet
contain the new COPY stuff... dunno how you get
around that one. (But then it doesn't happen very
often.)
Relax and have another Duvel :-)
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2005 11:17 PM
тАО05-16-2005 11:17 PM
Re: VMS 732-UPDATE-V4 - error parsing 'BLOCK_SIZE'
To avoid this situation, I do a
SET COMMAND/TABL=SYSLIBRARY:DCLTABLES
after installing the PCSI-patch.
I agree with you that the problem lies in the PCSI-patchkit, which should include this command in the procedure.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2005 11:36 PM
тАО05-16-2005 11:36 PM
Re: VMS 732-UPDATE-V4 - error parsing 'BLOCK_SIZE'
Michael already gave the answer.
Only, in this case, the problem is that UPDATE V4 is _ONE_ kit, that installs in _ONE_ pass. Therefore, one can not do SET COMMAND between two sub-kits.
Conclusion: in building the kit, after the COPY kit a SET COMMAND should have been issued, _OR_, the COPY kit should have been a prerequisite for UPDATE V4, like PCSI is.
Back to my previous statement: What happened to Quality Assurance? Has someone decided that *UX (or M$) level QA is sufficient for VMS also?????
Anyway, it s OK now.
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 12:18 AM
тАО05-17-2005 12:18 AM
Re: VMS 732-UPDATE-V4 - error parsing 'BLOCK_SIZE'
My understanding of PCSI is that it can reorder
the sequence of events that you create in the
.PCSI$DESC file. So you cannot rely on things
happening in the same sequence that you decide
they should occur. I am not aware of any way to
enforce the sequence of events.
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 01:05 AM
тАО05-17-2005 01:05 AM
Re: VMS 732-UPDATE-V4 - error parsing 'BLOCK_SIZE'
in that case, I think only one option is left for what SHOULD have been done:
- do NOT include the COPY patch in the UPDATE patch
&
- declare the COPY patch a prerequisite for the UPDATE patch
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 01:31 AM
тАО05-17-2005 01:31 AM
Re: VMS 732-UPDATE-V4 - error parsing 'BLOCK_SIZE'
Even if the COPY kit is a prerequisite you would
still have to install it twice (as I mentioned
above)
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 03:22 PM
тАО05-17-2005 03:22 PM
Re: VMS 732-UPDATE-V4 - error parsing 'BLOCK_SIZE'
Engineering are aware of this. It's benign, so they're not planning on fixing it until the next update kit is released (planned for November).
You can avoid the condition by installing VMS732_COPY-V0100 before installing the update kit.
Here's the explanation:
"When the VMS732_UPDATE-V0400 kit is installed, if the VMS732_COPY-V0100 kit was not previously installed, a user may see the following error:
%CLI-F-SYNTAX, error parsing 'BLOCK_SIZE'
-CLI-E-ENTNF, specified entity not found in command tables
...100
%SKPDAT, image data (records not beginning with "$") ignored
This error occurs when a post-installation file runs, after the kit has completed installation of all images. The integrity of the installation is not affected.
The reason the error occurs is that the UPDATE kit provides a COPY.CLD update to DCLTABLES and also a new APB.EXE file. When DCLTABLES is updated, PCSI should install the new DCLTABLES and perform a SET COMMAND to make the new commands available to the installation process. A regression in PCSI (which will be corrected in the next PCSI kit) prevents this from happening. When a kit provides a new APB.EXE file, the post-installation file performs a COPY/CONTIGUOUS on the new APB.EXE before performing a WRITEBOOT. Since the new COPY commands gave not been made available to the process, it is this COPY that is failing. The WRITEBOOT is executed successfully."