Conference azur::mcc

    Well I suppose it could be a bit more helpful but there are a limited
    number of fairly standard ways to fail creating a file, to wit:
    
    1) No write access to the device, volume, or directory (MCC_SYSTEM).
    
    2) No space on the device.
    
    3) Logical name MCC_SYSTEM, MCC_COMMON, or MCC_SPECIFIC setup wrong.

� 1) No write access to the device, volume, or directory (MCC_SYSTEM).

$ SET PROC/PRIV=ALL ?

� 2) No space on the device.

18�K blocks ?

� 3) Logical name MCC_SYSTEM, MCC_COMMON, or MCC_SPECIFIC setup wrong.

(LNM$SYSTEM_TABLE)

  "MCC_COMMON" = "SYS$COMMON:[MCC]"
  "MCC_NODE_IDP" = "49::"
  "MCC_SPECIFIC" = "SYS$SPECIFIC:[MCC]"
  "MCC_SYSTEM" = "MCC_SPECIFIC"
        = "MCC_COMMON"
  "MCC_TDF" = "+1:00"

RE: .0

>    In an attempt to use the YOURMM access module I typed the following...
>
>$ @sys$common:[syshlp.examples.mcc]mcc_yourmm_auto_tools msl ptb first
>

The Parse Table file .BPT is written to your current default directory.
Are you able to create files in that directory?  You weren't in the
sys$common:[syshlp.examples.mcc] directory, were you?

/keith

	:
	:
-->Update the parse tables

%MCCPTB-F-BPT, Unable to create Binary Parse Table (.BPT) file.
Fatal DECmcc error
  Error while running through the tools
$ sho quo
Disk quotas not enabled on this volume
$ sho proc/quo

11-OCT-1990 09:52:47.07   User: WATSON           Process ID:   22C000B9
                          Node: RC30             Process name: "Ross"

Process Quotas:
 Account name: WATSON
 CPU limit:                      Infinite  Direct I/O limit:       100
 Buffered I/O byte count quota:    131072  Buffered I/O limit:     100
 Timer queue entry quota:             128  Open file quota:        100
 Paging file quota:                 29051  Subprocess quota:        40
 Default page fault cluster:           16  AST quota:              323
 Enqueue quota:                       512  Shared file limit:        0
 Max detached processes:                0  Max active jobs:          0
$
$ sho def
  ROOT:[MCC]
$ sho log root
   "ROOT" = "Sys$Login_Device:[WATSON.]" (LNM$JOB_80650050)
$
$ sho dev Sys$Login_Device:

Device                  Device           Error    Volume         Free  Trans Mnt
 Name                   Status           Count     Label        Blocks Count Cnt
COUNTY$DUA1:            Mounted              0  DOSH_1           17150    10   6
$

Any ideas ?

Thanks.
Ross

    I just discovered that someone has changed the BPT output logic so
    that the specific reason for not being able to create the file is
    no longer given.
    
    I apologize for this waste of your time on behalf of the MCC group and
    will get this situation fixed asap.

    Thanks for the apology. Do you have any ideas how I can get the YOURMM
    example to work as we're getting nowhere with the MCC documentation.

Thanks
Ross

    I'm going to pass this over to the group that made the changes and see
    if they can figure it out.
    

In the version of the sys$common:[syshlp.examples.mcc]mcc_yourmm_auto_tools.com
that is on my system, the .BPT file is explicitly created in MCC_SYSTEM:

$!
$ PTB:
$ write sys$output " "
$ write sys$output "-->Update the parse tables"
$ write sys$output " "
$ manage/toolkit/parse_table MCC_SYSTEM:mcc_ptb_parser.bpt
$ if p2 .eqs. "PTB" then goto exit

Could you please try the following:

$ create mcc_system:mcc_ptb_parser.bpt

If DCL doesn't give you a more meaningful error message, give me a call at
DTN 226-5967 or send mail and we'll figure this out.

Pete

� $ create mcc_system:mcc_ptb_parser.bpt

    This doesn't work because...

	...SYS$SPECIFIC:[MCC] doesn't exist. I created this directory and now
    the thing gets futher than it did before.

    I don't know if it all worked because the machine crashed.

    I'll try again.

Ross (feeling a mite sheepish)

    Why are we creating the parser .bpt file (a read-only file) in
    mcc$specific?
    

re: -.1
Jim,

You aren't creating the parser's .bpt file in MCC_SPECIFIC; the .COM file 
creates it in MCC_SYSTEM, and the "standard" translation is 
<MCC_SPECIFIC, MCC_COMMON>.

Just checked this by redefining MCC_SYSTEM as <no-such-dir, MCC_COMMON>
(akin to the situation described).  Yup, you do get the 'unable to create' 
message, probably since RMS tries to create the file in the first directory of 
a searchlist, and gets an error writing to the non-existent directory.

re: .0
Not sure why SYS$SPECIFIC:[MCC] wouldn't have existed on that system; sounds 
like it should have been created during MCC installation....  You might want to
check other nodes in the cluster (assuming you're on one! :-) to make sure it's
there for all systems you're likely to be running on - before this bites you 
from another node!

		Helen

    To get aorund this you can modify the com file so as to use the
    default operation of PTB, which is to write to the current
    directory.
    

	Following on from Ross' original note, when we try to build the sample
	AM we get so far creating the parse tables and.......

[STONE.MCC] @mcc_sample_auto_tools ptb ptb

-->Update the parse tables

DECmcc Parse Table Builder
Component Version: X1.1.0

    Parse Table filename:       MCC_SYSTEM:MCC_PTB_PARSER.BPT
    Command Log Data filename:  MCC_PTB_PARSER.DAT
Processing entity 1
	.
	.
	.
Processing entity 9 21 36
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=00000008, PC
=00210072, PSL=03C00000
%MCC-E-OUTOFMEM, insufficient virtual memory available
%SYSTEM-E-ACCVIO, access violation, reason mask=00, virtual address=0000000A, PC
=0000000A, PSL=0000000F
Error while running through the tools

	Bill

    1) You ran out of VM.  See the release notes/doc for how much quota you
    need.
    
    2) There is (obviously) a bug in ptb where it accvio's after running
    out of VM.  Please QAR it.
    

    
    I will qar the system on this acc vio. From what you have given
    we can not tell where the access violation is happening (in the
    kernel or the tool). We can do some testing in an attempt to
    isolate the problem. Something is returning the OUTOFMEM message
    that PTB is displaying, the question is simply where the acc vio
    occurs.