How to access this file on ODS-5

[Peter Zeiszler]

Those familiar with Oracle or Jave might have a quick answer.

This is the filename
"DSA50:[ORACLE_10GKIT.stage.Components.oracle^.rsf.10^.2^.0^.1^.0.1.DataFiles]filegroup92.jar;1"

How would I access this file -- like even doing a Directory?
Using quotes around the name doesn't work.
The first ^ throws off set def, dir, etc.

[Steven Schweda · Accepted solution]

As usual, showing actual commands and actual
results would be more helpful than vague
"doesn't work" - "throws off" descriptions.

show process /parse_style

If it doesn't say "Parse Style: Extended",
then try:

set process /parse_style = extended


For example:

ALP $ cre /dir d5:[ORACLE_10GKIT.stage.Components.oracle^.rsf.10^.2^.0^.1^.0.1.D
ataFiles]
%DCL-W-DIRECT, invalid directory syntax - check brackets and other delimiters
\D5:[ORACLE_10GKIT.STAGE.COMPONENTS.ORACLE\
ALP $ sh proc /pars

26-SEP-2007 21:31:45.27 User: SYSTEM Process ID: 2027D919
Node: ALP Process name: "_FTA30:"

Soft CPU Affinity: off

Parse Style: Traditional
ALP $ set process /parse_style = extended
ALP $ cre /dir d5:[ORACLE_10GKIT.stage.Components.oracle^.rsf.10^.2^.0^.1^.0.1.D
ataFiles]
ALP $

[Peter Zeiszler]

You hit it.

$ dir DSA50:[ORACLE_10GKIT.stage.Components.oracle^.rsf.10^.2^.0^.1^.0.1.DataFiles]filegroup92.jar;1
%DCL-W-DIRECT, invalid directory syntax - check brackets and other delimiters
\DSA50:[ORACLE_10GKIT.STAGE.COMPONENTS.ORACLE\

$ show proc/parse

27-SEP-2007 11:00:15.82 User: SYSTEM Process ID: 0001459A
Node: SIMBA Process name: "SYSTEM"

Parse Style: Traditional

-----
$ set proc/pars=ext

$ dir DSA50:[ORACLE_10GKIT.stage.Components.oracle^.rsf.10^.2^.0^.1^.0.1.DataFiles]filegroup92.jar;1

Directory DSA50:[ORACLE_10GKIT.stage.Components.oracle^.rsf.10^.2^.0^.1^.0.1.DataFiles]

filegroup92.jar;1

--------------

Thanks.

[Steven Schweda]

I set /parse = extended in my various
LOGIN.COM files. The only problem I have is
when some procedure or other sets it back to
traditional, and leaves it that way. In
fact, that had happened in the DECterm where
I ran that test, so I was a bit startled when
it failed for me the first time. (I was
expecting to have to set it back to
traditional myself before it would fail, but
someone had "helped" me out when I wasn't
looking.)

[Peter Zeiszler]

We also had to do use the "set proc/case=blind" in some cases for client command files.