HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

spaces replaced by __20 after pathworks upgrade

 
SOLVED
Go to solution
robert70
Valued Contributor

spaces replaced by __20 after pathworks upgrade

Upgraded Pathworks from 6.0c to 7.3B and files created by word *.docs are now showing this type of changes

before upgrade:-
various upgrade notes.doc

after upgrade:-
various__20upgrade__20notes.doc

can anything be done to resolve this? apart from obviously changing each file manually.
thanks


18 REPLIES
robert70
Valued Contributor

Re: spaces replaced by __20 after pathworks upgrade

also odd things happening with long named files after upgrade (also upgraded vms 7.3-2 to vms 8.3)

doing a directory of files we have

before upgrade:-
QUESTIONNAIRE_ADDITIONAL_NOTES_29-2017.DOC

and after upgrade:-
QUESTIONNAIRE__20__28ADDITIONAL__20NOTE.S__29__20-__2017__2E02__2E00__2EDOC

?
Ian Miller.
Honored Contributor
Solution

Re: spaces replaced by __20 after pathworks upgrade

ODS5 disk?

____________________
Purely Personal Opinion
robert70
Valued Contributor

Re: spaces replaced by __20 after pathworks upgrade

AHH YES JUST UPGRADED THIS TO AN ODS5-DISK
does this have limitations on length of names?
Ian Miller.
Honored Contributor

Re: spaces replaced by __20 after pathworks upgrade

no, the opposite - ODS5 has allows a greater variety of names.

However you may need to tell Advanced Server to act differently.

(BTW do you have V7.3B ECO2?)

____________________
Purely Personal Opinion
robert70
Valued Contributor

Re: spaces replaced by __20 after pathworks upgrade

NO ECO2
just 7.3B
Brad McCusker
Respected Contributor

Re: spaces replaced by __20 after pathworks upgrade

Hello Robert,

Back in the day, I used to wonder why we wrote documentation - folks never read it I thought. And they still don't read it, apparently. ;^)

Seeing as you installed V7.3B, I think it appropriate to point you to the V7.3B Server Installation and Configuration Guide. You'll find it at http://h71000.www7.hp.com/doc/82final/6540/6540pro.html.

In particular, read Chapter 5.8 - "Converting Encoded File Names from ODS-2 to ODS-5".

You see, ODS-2 does not support extended file names and things like spaces in file names. So, PATHWORKS and Advanced Server will encode the non-ODS2 compatible characters in a file name by replacing them with __XX where XX=ascii hex value of the character. for example, a space in a file name is encoded as "__20" (that's underscore underscore two zero).

Now that you converted the disk to ODS-5 and ODS-5 supports the extended file names, there is no need for the encoding and Advanced Server assumes there is no encoding. So when it sees "__20" it no longer changes it to a " " (space), it leaves it as "__20" which is exactly what you see.

You need to run the PWCONVERT utility against the disk to get rid of all those encoded characters.

Hope this helps,

Brad McCusker
Software Concepts International
www.sciinc.com

Brad McCusker
Software Concepts International
Brad McCusker
Respected Contributor

Re: spaces replaced by __20 after pathworks upgrade

This does not make sense:
>>before upgrade:-
>>QUESTIONNAIRE_ADDITIONAL_NOTES_29-2017.DOC

>>and after upgrade:-
>>QUESTIONNAIRE__20__28ADDITIONAL__20NOTE.S__29__20-__2017__2E02__2E00__2EDOC

Are you showing us what the client PC sees, or what you see from VMS?

Did this disk get converted from ODS-2 to ODS-5?

"QUESTIONNAIRE_ADDITIONAL_NOTES_29-2017.DOC" is a legal ODS-2 file name. There should have been no encoding for that file name which is why I say something doesn't make sense with regards to that name.

Are there many other files like that one?

Brad McCusker
Software Concepts International
www.sciinc.com
Brad McCusker
Software Concepts International
robert70
Valued Contributor

Re: spaces replaced by __20 after pathworks upgrade

This does not make sense:
>>before upgrade:-
>>QUESTIONNAIRE_ADDITIONAL_NOTES_29-2017.DOC

>>and after upgrade:-
>>QUESTIONNAIRE__20__28ADDITIONAL__20NOTE.S__29__20-__2017__2E02__2E00__2EDOC



Sorry Brad this was showing

QUESTIONNAIRE ADDITIONAL NOTES 29-2017.DOC

before the upgrade



>>Are you showing us what the client PC sees, or what you see from VMS?

this is showing both what the client sees and what vms sees - both the same

It was the system disk that was upgraded from ODS2 to ODS5 - the user disk which contains the files mentioned above were already ODS5

>>Are there many other files like that one?

There are many files yes
robert70
Valued Contributor

Re: spaces replaced by __20 after pathworks upgrade

$ CHAS:SYSTEM> pwconvert
_FILENAME: FAQ__20184__20-__20SAUDI__20QUARTERLY__.20REBALANCING_NOTES__2EDOC
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000000690
0000, PC=FFFFFFFF8083B424, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
LIBRTL 0 000000000000B424 FFFFFFFF8083B424
DECC$SHR_EV56 0 000000000005FD24 FFFFFFFF80AF7D24
DECC$SHR_EV56 0 000000000002994C FFFFFFFF80AC194C
DECC$SHR_EV56 0 0000000000133284 FFFFFFFF80BCB284
DECC$SHR_EV56 0 0000000000134BA4 FFFFFFFF80BCCBA4
DECC$SHR_EV56 0 000000000000E4C8 FFFFFFFF80AA64C8
DECC$SHR_EV56 0 000000000000BD00 FFFFFFFF80AA3D00
DECC$SHR_EV56 0 000000000010CC08 FFFFFFFF80BA4C08
DECC$SHR_EV56 0 00000000001138A0 FFFFFFFF80BAB8A0
PWRK$CNVTOHFS PWRK$CNVTOHFS main 37852 000000000000094C 000000000003094C
PWRK$CNVTOHFS PWRK$CNVTOHFS __main 0 0000000000000070 0000000000030070
0 FFFFFFFF8037FCE4 FFFFFFFF8037FCE4
%TRACE-I-END, end of TRACE stack dump
robert70
Valued Contributor

Re: spaces replaced by __20 after pathworks upgrade

i get a failure when using pwconvert on a file that has had its name changed - see above
robert70
Valued Contributor

Re: spaces replaced by __20 after pathworks upgrade

obviously because the disk which has corrupted file names was already ODS5 I am getting this on a pwconvert also.....

$pwconvert *.*

File is not ODS-2 - $1$DGA1:[PCCOMMON.FAQ]FAQ__20001__20-__20157__20__20INDEX.DO
C;1

etc...........
Hans Hosang
Frequent Advisor

Re: spaces replaced by __20 after pathworks upgrade

Robert,

You should have run this command right after the upgrade.
Now several files have been touched by Advanced Server and now have an ODS5 header.

There are 3 undocumented switches to overcome this issue.
If either of the following checks fail, PWCONVERT refuses to perform a conversion.
- Is the device ODS5 ?
- Is the file's fileheader NOT already an ODS5 type?
- Does the file have a Pathworks ACE ?

This can be bothersome. Accessing a file (even a $type command) may already be enough to have OpenVMS automatically change the fileheader layout from ODS2 to ODS5.

Each of the above checks can be overruled with the /DISABLE qualifier:

$ PWCONVERT /DISABLE=(ods5, struct, ace)

where disable=ods5: do not check if the device is ODS5
disable=struct: do not check if the fileheader is ODS5
disable=ace: do not check if the file has a PWRK ace.

Normally it will suffice to use /DISABLE=(struct) or /DISABLE=(struct,ace).
Using /DISABLE=ods5 is not recommended.

Hope this helps.
OpenVMS -Windows - UNIX integration
Hans Hosang
Frequent Advisor

Re: spaces replaced by __20 after pathworks upgrade

Robert,

the crash you had in pwconvert is listed in the solved problems of V7.3B-eco1.

So I guess you didn't upgrade to the latest ECO version but to V7.3B plain.

Am I correct?
$ pwver should list V7.3-210B for the latest ECO version.
OpenVMS -Windows - UNIX integration
robert70
Valued Contributor

Re: spaces replaced by __20 after pathworks upgrade

thanks hans

this command worked great thanks

>> $ PWCONVERT /DISABLE=(struct, ace)


robert70
Valued Contributor

Re: spaces replaced by __20 after pathworks upgrade

>>$pwver should list V7.3-210B for the latest ECO version


we have V7.3-200B


Hans Hosang
Frequent Advisor

Re: spaces replaced by __20 after pathworks upgrade

Your version is outdated, Robert.
I'd upgrade to V7.3B-eco1 asap.

You can download it from our web:
http://www11.itrc.hp.com/service/patch/patchDetail.do?admit=109447626+1289298124257+28353475&patchid=ADVANCSERV-V0703-B1

OpenVMS -Windows - UNIX integration
robert70
Valued Contributor

Re: spaces replaced by __20 after pathworks upgrade

THANKS HANS - WILL DO
robert70
Valued Contributor

Re: spaces replaced by __20 after pathworks upgrade

THANKS ALL FOR HELP