OpenVMS Alpha Galaxy Guide
←Previous Next→ Contents Tables Close Help
  9.14  GCU System Messages

                               Margie:
      These messages need to be in alphabetical order based
      on the message name gcu-x-MESSAGENAME.

  %GCU-E-SUBPROCHALT,  Subprocess  halted;  See  GCU.LOG.
    The  GCU  has  launched  a  user-defined  subprocess  which  has  terminated
    with  error  status.   Details  may  be  found  in  the  file  GCU.LOG.

  %GCU-S-SUBPROCTERM,  Subprocess  terminated
    The  GCU  has  launched  a  user-defined  subprocess  which  has  terminated.

  %GCU-I-SYNCMODE,  XSynchronize  activated
    The  GCU  has  been  invoked  with  X-windows  synchronous  mode  enabled.

    This  is  a  development  mode  which  is  not  generally  used.
  %GCU-W-NOCPU,  Unable  to  locate  CPU

    A  migration  action  was  initiated  which  involved  an  unknown  CPU.   This
    can  result  from  engaging  a  model  which  contains  invalid  CPU  identifiers
    for  the  current  system.
  %GCU-E-NORULESET,  Ruleset  not  found:

    The  GCU  was  unable  to  locate  the  Galaxy  Configuration  Ruleset  in
    SYS$MANAGER:GALAXY.GCR.   New  versions  of  this  file  can  be  downloaded
    from  the  OpenVMS  Galaxy  web  page.
  %GCU-E-NOMODEL,  Galaxy  configuration  model  not  found:

    The  specified  Galaxy  Configuration  Model  was  not  found.   Check  your
    command  line  model  file  specification.

  %GCU-W-XTOOLKIT,  X-Toolkit  Warning:
    The  GCU  has  intercepted  an  X-Toolkit  warning.   You  may  or  may  not  be
    able  to  continue,  depending  on  the  type  of  warning.

  %GCU-S-ENGAGED,  New  Galaxy  configuration  model  engaged
    The  GCU  has  successfully  engaged  a  new  Galaxy  Configuration  Model.

  %GCU-E-DISENGAGED,  Unable  to  engage  Galaxy  configuration  model
    The  GCU  has  failed  to  engage  a  new  Galaxy  Configuration  Model.   This
    can  happen  when  a  specified  model  is  invalid  for  the  current  system,  or
    when  other  system  activities  prevent  the  requested  resource  assignments.
  %GCU-E-NODECW,  DECwindows  is  not  installed.

    The  current  system  does  not  have  the  required  DECwindows  support.
  %GCU-E-HELPERROR  Help  subsystem  error.

    The  DECwindows  Help  system  (Bookreader)  encountered  an  error.
  %GCU-E-TOPICERROR  Help  topic  not  found.

    The  DECwindows  Help  system  could  not  locate  the  specified  topic.
  %GCU-E-INDEXERROR  Help  index  not  found.

    The  DECwindows  Help  system  could  not  locate  the  specified  index.
  %GCU-E-UNKNOWN_COMPONENT:  {name}

    The  current  model  contains  reference  to  an  unknown  component.   This
    can  result  from  model  or  ruleset  corruption.   Search  for  the  named
    component  in  the  ruleset  SYS$MANAGER:GALAXY.GCR.   If  it  is  not  found,
    download  a  new  one  from  the  OpenVMS  Galaxy  web  site.   If  the  problem
    persists,  delete  and  recreate  the  offending  model.

  %GCU-I-UNASSIGNED_HW:  Found  unassigned  {component}"
    The  GCU  has  detected  a  hardware  component  which  is  not  currently
    assigned  to  any  Galaxy  instance.   This  may  result  from  intentionally
    leaving  unassigned  resources.   Note  the  message  and  continue  or
    assign  the  hardware  component  from  the  primary  Galaxy  console  and
    reboot.
  %GCU-E-UNKNOWN_KEYWORD:  {word}

    The  GCU  has  parsed  an  unknown  keyword  in  the  current  model  file.   This
    can  only  result  from  model  file  format  corruption.   Delete  and
    recreate  the  offending  model.
  %GCU-E-NOPARAM:  Display  field  {field  name}

    The  GCU  has  parsed  an  incomplete  component  statement  in  the  current
    model.   This  can  only  result  from  model  file  format  corruption.
    Delete  and  recreate  the  offending  model.

  %GCU-E-NOEDITFIELD:  No  editable  field  in  display.
    The  GCU  has  attempted  to  edit  a  component  parameter  which  is  undefined.
    This  can  only  result  from  model  file  format  corruption.   Delete  and
    recreate  the  offending  model.

  %GCU-E-UNDEFTYPE,  Undefined  Parameter  Data  Type:  {type}
    The  GCU  has  parsed  an  unknown  data  type  in  a  model  component  parameter.
    This  can  result  from  model  file  format  corruption  or  incompatible
    ruleset  for  the  current  model.   Search  the  ruleset  SYS$MANAGER:GALAXY.GCR
    for  the  offending  datatype.   If  not  found,  download  a  more  recent
    ruleset  from  the  OpenVMS  Galaxy  web  site.   If  found,  delete  and
    recreate  the  offending  model.
  %GCU-E-INVALIDMODEL,  Invalid  model  structure  in:  {model  file}

    The  GCU  attempted  to  load  an  invalid  model  file.   Delete  and  recreate
    the  offending  model.
  %GCU-F-TERMINATE  Unexpected  termination.

    The  GCU  encountered  a  fatal  DECwindows  event.
  %GCU-E-GCTLOOP:  Configuration  Tree  Parser  Loop

    The  GCU  has  attempted  to  parse  a  corrupt  configuration  tree.   This
    may  be  a  result  of  console  firmware  or  operating  system  fault.

  %GCU-E-INVALIDNODE:  Invalid  node  in  Configuration  Tree
    The  GCU  has  parsed  an  invalid  structure  within  the  configuration  tree.
    This  can  only  result  from  configuration  tree  corruption  or  revision
    mismatch  between  the  ruleset  and  console  firmware.

  %GCU-W-UNKNOWNBUS:  Unknown  BUS  subtype:  {type}
    The  GCU  has  parsed  an  unknown  bus  type  in  the  current  configuration
    tree.   This  can  only  result  from  revision  mismatch  between  the
    ruleset  and  console  firmware.

  %GCU-W-UNKNOWNCTRL,  Unknown  Controller  type:  {type}
    The  GCU  has  parsed  an  unknown  controller  type  in  the  current  configuration
    tree.   This  can  only  result  from  revision  mismatch  between  the
    ruleset  and  console  firmware.
  %GCU-W-UNKNOWNCOMP,  Unknown  component  type:  {type}

    The  GCU  has  parsed  an  unknown  component  type  in  the  current  configuration
    tree.   This  can  only  result  from  revision  mismatch  between  the
    ruleset  and  console  firmware.
  %GCU-E-NOIFUNCTION,  Unknown  internal  function

    The  user  has  modified  the  ruleset  file  and  specified  an  unknown
    internal  GCU  function.   Correct  the  ruleset  or  download  a  new  one
    from  the  OpenVMS  Galaxy  web  page.

  %GCU-E-NOEFUNCTION,  Missing  external  function
    The  user  has  modified  the  ruleset  file  and  specified  an  unknown
    external  function.   Correct  the  ruleset  or  download  a  new  one
    from  the  OpenVMS  Galaxy  web  page.

  %GCU-E-NOCFUNCTION,  Missing  command  function
    The  user  has  modified  the  ruleset  file  and  specified  an  unknown
    command  procedure.   Correct  the  ruleset  or  download  a  new  one
    from  the  OpenVMS  Galaxy  web  page.

  %GCU-E-UNKNOWN_COMPONENT:  {component}

    The  GCU  has  parsed  an  unknown  component.   This  can  result  from
    ruleset  corruption  or  revision  mismatch  between  the  ruleset  and
    console  firmware.
  %GCU-E-BADPROP,  Invalid  ruleset  DEVICE  property

    The  GCU  has  parsed  an  invalid  ruleset  component  statement.   This  can
    only  result  from  ruleset  corruption.   Download  a  new  one  from  the
    OpenVMS  Galaxy  web  page.
  %GCU-E-BADPROP,  Invalid  ruleset  CHART  property

    The  GCU  has  parsed  an  invalid  chart  statement.   This  can
    only  result  from  ruleset  corruption.   Download  a  new  one  from  the
    OpenVMS  Galaxy  web  page.

  %GCU-E-BADPROP,  Invalid  ruleset  INTERCONNECT  property
    The  GCU  has  parsed  an  invalid  ruleset  interconnect  statement.   This  can
    only  result  from  ruleset  corruption.   Download  a  new  one  from  the
    OpenVMS  Galaxy  web  page.

  %GCU-E-INTERNAL  Slot  {slot  detail}
    The  GCU  has  encountered  an  invalid  datatype  from  a  component  parameter.
    This  can  result  from  ruleset  or  model  corruption.   Download  a  new  one
    from  the  OpenVMS  Galaxy  web  page.   If  the  problem  persists,  delete  and
    recreate  the  offending  model.
  %GCU-F-PARSERR,  {detail}

    The  GCU  encountered  a  fatal  error  while  parsing  the  ruleset.   Download
    a  new  one  from  the  OpenVMS  Galaxy  web  page.
  %GCU-W-NOLOADFONT:  Unable  to  load  font:  {font}

    The  GCU  could  not  locate  the  specified  font  on  the  current  system.
    A  default  font  will  be  used  instead.
  %GCU-W-NOCOLORCELL:  Unable  to  allocate  color

    The  GCU  is  unable  to  access  a  colormap  entry.   This  can  result  from
    a  system  with  limited  color  support  or  from  having  an  excessive  number
    of  graphical  applications  open  at  the  same  time.

   GCU-E-NOGALAXY,  This  system  is  not  configured  as  a  Galaxy.
    Description:

       The  user  has  issued  the  CONFIGURE  GALAXY/ENGAGE  command  on  a
       system  which  is  not  configured  for  Galaxy  operation.
    User  Action:

       Configure  your  system  for  Galaxy  operation  using  the  procedures
       described  in  the  OpenVMS  Galaxy  Guide.   If  you  only  want  to  run  a
       single-instance  Galaxy,  enter  CONFIGURE  GALAXY  without  the
       /ENGAGE  qualifier  and  follow  the  instructions  provided  by  the
       Galaxy  Configuration  Utility.

  %GCU-E-ACTIONNOTALPHA  GCU  actions  require  OpenVMS  Alpha
    A  GCU  user  has  attempted  to  invoke  a  Galaxy  configuration  operation
    on  an  OpenVMS  VAX  system.

  %GCU-I-ACTIONBEGIN  at  {time},  on  {instance}  {mode}
    This  informational  message  indicates  the  start  of  a  configuration
    action  on  the  specified  Galaxy  instance.   Note  that  many  actions
    require  collaboration  between  command  environments  on  two  separate

    Galaxy  instances,  thus,  you  may  encounter  two  of  these  messages,  one
    per  instance  involved  in  the  operation.   The  mode  argument  indicates
    which  instance  is  local  versus  remote.
  %GCU-S-ACTIONEND   at  {time},  on  {nodename}

    This  is  the  normal  successful  completion  message  following  a  Galaxy
    configuration  action.   Note  that  many  actions  require  collaboration
    between  command  environments  on  two  separate  Galaxy  instances,  thus,  you
    may  encounter  two  of  these  messages,  one  per  instance  involved  in  the
    operation.
  %GCU-S-ACTIONEND,  Exiting  GCU$ACTIONS  on  ^Y

    Indicates  that  the  user  has  aborted  a  Galaxy  configuration  action
    using  Control-Y.

  %GCU-S-ACTIONEND,  Exiting  GCU$ACTIONS  on  error  {message}
    Indicates  that  a  Galaxy  configuration  action  terminated  with  error
    status  as  indicated  by  the  message  argument.

  %GCU-E-ACTIONUNKNOWN  no  action  specified
    Indicates  that  the  GCU$ACTIONS.COM  procedure  was  called  improperly.
    It  is  possible  that  the  command  procedure  has  been  corrupted  or  is
    out  of  revision  for  the  current  system.

  %GCU-E-ACTIONNOSIN  no  source  instance  name  specified

    Indicates  that  the  GCU$ACTIONS.COM  procedure  was  called  improperly.
    It  is  possible  that  the  command  procedure  has  been  corrupted  or  is
    out  of  revision  for  the  current  system.
  %GCU-E-ACTIONBAD  failed  to  execute  the  specfied  action

    Indicates  that  a  Galaxy  configuration  action  aborted  due  to  an
    indeterminate  error  condition.   Review  related  screen  messages  and
    verify  that  the  necessary  proxy  accounts  have  been  established.
  %GCU-E-INSFPRIVS,  Insufficient  privileges  for  attempted  operation

    An  underprivileged  user  has  attempted  to  perform  a  Galaxy  configuration
    action.   Typically,  these  actions  are  performed  from  within  the  system
    managers  account.   OPER  and  SYSPRV  privileges  are  required.

  %GCU-E-NCF  network  connect  to  {instance}  failed
    An  error  has  occurred  trying  to  open  a  DECnet  task-to-task  connection
    between  the  current  and  specified  instances.   Review  related  screen
    messages  and  verify  that  the  necessary  proxy  accounts  have  been
    established.
←Previous Next→ Contents Tables Close Help