# This file contains various configuration information for the ProdExec
# and ProdExecEditor applications.
#
# Initial version: 03/03/10 by Rob Janes

# Stand - The stand where an instance of ProdExec is being run.  The
# value should already be defined in the database.
prodexec.stand S_1

# Stand type - A site may have different types of stands.  The value
# should already be defined in the database.
prodexec.standType AMMPS_Sample

# Building - The building where ProdExec is being run.  This should
# aready be defined in the database.
prodexec.building ABC

# Room - The room where ProdExec is being run.  This should already be
# defined in the database.
prodexec.room 123

# Display script location - The default location to look for display
# configuration files to be displayed by ProdExec.
prodexec.displays /specs/OpDisplays

# gp_test scripts location - The default location to look for gp_test
# scripts to be executed by ProdExec.
prodexec.gp_tests /specs/gp

# Scripts location - The default location to look for script command
# files to be executed by ProdExec.
prodexec.scripts /specs/cmds

# Standard ProdExec display - The single display configuration file
# displayed near the top of the ProdExec application.  This should be
# in the directory pointed to by prodexec.displays.
prodexec.standardProdExecDisplay prod_exec_standard_display.dsp

# Stand display - The single display configuration file displayed
# at the bottom of the ProdExec application.  This should be in the
# directory pointed to by prodexec.displays.
prodexec.standDisplay display_1

# Manufacturer for ModelDef table.  The default value for the
# manufacturer value inserted into the ModelDef table.
prodexec.manufacturer  Cummins

# Application being executed.  The prodexec supports multiple
# applications but there currently is only one, ammps.  Further users
# might have different values for this.
prodexec.application  ammps

# Location of files to be processed by ProdExec extdatman.  ProdExec
# will store files here and the external data manager instance will
# access them and load them into the database.
prodexec.extdatman.home ./data/prodexec

# Base location of files generated by scripts or gp_tests, perhaps for
# post-step or post-sequence analysis.
prodexec.data_storage ./data/storage

# **********************************************************************
# Interface names - application to CyFlex.

# Name of the event signalling a user id bar code scan.
prodexec.user_event_name userScanEvent

# Name of the event signalling a uut bar code scan.
prodexec.uut_event_name  uutScanEvent

# Variable name holding the scanned user data.
prodexec.user_data_name userScanData

# Variable name holding the scanned uut data.
prodexec.uut_data_name  uutScanData

# *******************
# Interface names - application to gp_test or shell scripts.

# Procedure fault code returned in this integer variable.
prodexec.ProcedureReturnFaultCode ProcedureReturnFaultCode

# Procedure diagnostic notes returned in this string variable.
prodexec.ProcedureReturnDiagNotes ProcedureReturnDiagNotes

# Procedure ran flag returned in this logical variable.
prodexec.ProcedureRan ProcedureRan

# Procedure passed flag returned in this logical variable.
prodexec.ProcedurePassed ProcedurePassed

# The directory where step data files, e.g. logger files, should be
# stored.  Set by ProdExec before a step is executed.
prodexec.StepStoragePath StepStoragePath

# The directory where sequence data files should be stored.  Set by
# ProdExec before a sequence begins executing.
prodexec.SeqStoragePath SeqStoragePath

# *******************
# gp_test events

# Event sent to a gp_test to indicate it should abort.
prodexec.ProcedureInAbortEvent abort

# Event received from a gp_test indicating that it completed.
prodexec.ProcedureOutEndEvent procdr_end

# *******************
# "Display" variable names.  While not necessarily displayed, these
# correspond to data which might appear in the
# prodexec.standardProdExecDisplay display.

prodexec.uut.model          model_number
prodexec.uut.serial_number  serial_number
prodexec.user               user
prodexec.sequence_name      seq_name
prodexec.step_name          step_name
prodexec.procedure_name     procedure
prodexec.sequence_status    sequence_stat
prodexec.time_in_step       time_in_step
prodexec.operator_needed_in op_needed_in
prodexec.mode               admin_mode
prodexec.step_order         step_order

# *******************
# Termination related settings

# Variable name which will be set at the start of a step to the
# StepDef.terminationRule value.
prodexec.terminate_rule_var terminate_rule

# Variable name which will be set at the start of a step to the
# StepDef.TerminationValue value.
prodexec.terminate_threshold terminate_threshold

# *******************
# Font size for the main panel sequence display.
prodexec.sequence_panel_font_size   20

# *******************
# "R12" settings

# Is an R12 database available for use: true / false
# Remote sites might not have an R12 database.  This would require only
# manual UUT data entry.
prodexec.product_db_avail   true

# Database access information

# Name of the view to be accessed for R12 / UUT information.
prodexec.r12_view           R12.XXWMS_FRIDLEY_OPERATIONS_TC
# JDBC connect string for the database holding R12 information.
prodexec.r12_connect_string jdbc:oracle:thin:@cmx035:1521/LTS
# Login name for R12 data.
prodexec.r12_login          ammpsprodexec
# Password for R12 data login.
prodexec.r12_password       ammpsprodexec

# Time in seconds between connection failure retry attempts
prodexec.r12_retry_interval 20

# Number of R12 database connection retrys before reprompting user
prodexec.r12_retrys         30

# Specs file for R12 / UUT data fields.
prodexec.uut_specs     ../../../../specfilegui/xmlfiles/prodexec/UUT.xml
