Conference azur::mcc

    I do not understand all of the limitations, but I believe the release
    notes explain the case and datatype sensitivities of the
    recording/exporting functions. I think (and Sam will have to correct me
    if I am wrong) that you have to export using the same instance
    name/address as you used when creating the recording.
    

	RE:.1

>    ....that you have to export using the same instance
>    name/address as you used when creating the recording.

	Yes and No.

	Record/Export directive and all other Historian/Exporter directives
        works differently in term of instance sensitivity.

	Record/Export directive supports everything what is supported by
	Show ... All Ident for the target entity. So if Show ... All Ident
	is case sensitive the Record/Export is case sensitive too.

	All other Historian/Exporter directives (and Past Time Show) use 
	Private and/or Historical MIR to get information about the target
	entity. All entries in the MIR for a particular entity are created 
	using output from Directory command. Directory returns a fullname
	in the the same case as this entity had been registered.
	The only exception is Node4 name: it can be entered using or lower
	or upper case(but you can not mix the case!).

	Jill is right this is explained in the release notes.

	RE: .0

	
>MCC> show export node4 VAX1 export target export_file. 
>
>Will display exporting information, But if you specify the full node4
>pathname. 
>
>ie. MCC> SHOW EXPORT NODE4 .dna_node.vax1 EXPORT TARGET export_file
>
>Node4 VAXA_NS:.dna_node.VAX1
>
><date+time>
>Repositories do not exist

	1. Are you sure that text is "Repositories do not exist" but not
	   "No exporting for the specified entity "?

	   "Repositories do not exist" indicates that you'd never asked to 
	   export data to the specified EXPORT TARGET database.

	2. Try to do Directory for the NODE4 .dna_node.vax1 and use
	   "Registered Name" argument in the response as instance in the
	   Show Exporting.

	3. Using IMPM, please, be sure that entity name on your map is the
	   same as "Registered Name" argument in the response in Directory
	   command,e.g. the same as this entity has been registered.
	   I think that this is a problem you have.

>	- define/system export_file mcc_export.rdb.
>	- submitted the background job with export_file as the parameter.
>	- export node4 * export target export_file, start time = 00:02 ,
>                    in domain = <domain>.

	You can not do this.
	
	   1. A parameter to the Background process must be a valid Rdb/VMS
	      filename( but NOT a logical). See Historical Data Services Use
	      page 2-8.

	   2. Export Target argument must match the database you used
	      in the Background process. See Historical Data Services Use
	      page 2-14.

	   3. For default database name in the Export Target argument you must
	      use the logical MCC_EXPORT_RDB_FILE. See Historical Data Services
	       Use page 2-14.

	So if you want to use logical:

	- define/system mcc_export_rdb_file mcc_export.rdb.
	- submitted the background job with mcc_export.rdb as the parameter.
	- export node4 * export  start time = 00:02 ,in domain = <domain>.

	  Files mcc_export.rdb and mcc_export.snp will be created in the 
	  default directory for the Background process.


	SAm
    

    For V1.1, the logical name for the export target has to be a process
    logical and not a system logical. Hopefully fixed for 1.2
    
    s/rob

    Thanks for the valued replies and sorry for the delay in response but I was 
    off ill for a few days.
    
    I put to use the information supplied and here is what I found out.
    
    A DIRECTORY on the node listed it as "PV05_NS:.dna_node.PV05". On the 
    Iconic map it was displayed as ".dna_node.pv05"
    
    Exporting was started using the  iconic map and when a subsequent
    Show Exporting was performed. It returned a "No Exporting for the 
    Specified Entity" (as corrected in .2).
    
    From the command line you could do a show exporting using the node
    Synonym (U/Lcase) and it would show exporting active. Or using the
    Show Exporting node4 .dna_node.PV05 worked as well, but no other
    combinations.
    
    We deleted the node and re-added it using .dna_node.pv05, all in
    lowercase and verified the information with the directory command.
    We started exporting again using the Iconic Map and we were able to
    see the exporting using the IMPM and through the FCL. Thanks again for
    the advice, as it was spot on.
    
    The nodes were originally pre-registered using the MCC_DNS_SETUP.COM
    option 2. This registered the PHASE4 nodes in mixed cases. 
    
    ie. an extract from my command file.
    
    "REGISTER NODE4 brooky_ns:.dna_node.VAX0 SYNONYM=VAX0 !IDP=49::
    ADDRESS=1.0160"
    
    I couldn't find the Historical Data Serverices Use manual to get some
    more info. Just must have been one of the manuals I was missing, but
    soon will acquire...
    
    We have implemented the use of the MCC_EXPORT_RDB_FILE logical and
    using the full directory spec as the parameter for the background
    process. All is now working really well.
    
    Thanks,
    Niguel