Method Verb and Script Location

deeabar

On a docbase that I recently inherited for maintanence, I see this as the verb on a custom method - "dmbasic -eXYZCustomMethod" and I cannot find anything that resembles a custom script in $DM_HOME/bin. Where can I find the actual custom script?

ldallas

Does the use_method_content attribute of the method object = T. If so then its stored as content of that object.

deeabar

Lee, checked, no luck... the attribute is false.

sbickle

Post a dump of the dm_method object here

deeabar

USER ATTRIBUTES

  object_name                : Render Method
  title                      : Render Method
  subject                    : Rendition requests
  authors                  []: <none>
  keywords                 []: <none>
  resolution_label           :
  owner_name                 : dmnvmirs
  owner_permit               : 7
  group_name                 : docu
  group_permit               : 5
  world_permit               : 1
  log_entry                  :
  acl_domain                 : dmnvmirs
  acl_name                   : mirs_default_acl
  language_code              :
  method_verb                : dmbasic -eXYZCustomMethod
  method_args              []: <none>
  timeout_min                : 100
  timeout_max                : 4200
  timeout_default            : 3600
  launch_direct              : F
  launch_async               : T
  trace_launch               : T
  run_as_server              : T
  use_method_content         : F
  method_type                :
  use_method_server          : F

SYSTEM ATTRIBUTES

  r_object_id                : 1000b60380103990
  r_object_type              : dm_method
  r_creation_date            : 1/21/2006 16:17:27
  r_modify_date              : 2/6/2008 13:20:11
  r_modifier                 : dmadmin
  r_access_date              : 4/16/2007 16:15:35
  r_composite_id           []: <none>
  r_composite_label        []: <none>
  r_component_label        []: <none>
  r_order_no               []: <none>
  r_link_cnt                 : 0
  r_link_high_cnt            : 0
  r_assembled_from_id        : 0000000000000000
  r_frzn_assembly_cnt        : 0
  r_has_frzn_assembly        : F
  r_is_virtual_doc           : 0
  r_page_cnt                 : 0
  r_content_size             : 0
  r_lock_owner               :
  r_lock_date                : nulldate
  r_lock_machine             :
  r_version_label         [0]: 1.2
                          [1]: CURRENT
  r_immutable_flag           : F
  r_frozen_flag              : F
  r_has_events               : F
  r_creator_name             : dmnvmirs
  r_is_public                : F
  r_policy_id                : 0000000000000000
  r_resume_state             : 0
  r_current_state            : 0
  r_alias_set_id             : 0000000000000000
  r_full_content_size        : 0

APPLICATION ATTRIBUTES

  a_application_type         :
  a_status                   :
  a_is_hidden                : F
  a_retention_date           : nulldate
  a_archive                  : F
  a_compound_architecture    :
  a_link_resolved            : F
  a_content_type             :
  a_full_text                : T
  a_storage_type             : filestore_01
  a_special_app              :
  a_effective_date         []: <none>
  a_expiration_date        []: <none>
  a_publish_formats        []: <none>
  a_effective_label        []: <none>
  a_effective_flag         []: <none>
  a_category                 :
  a_is_template              : F
  a_controlling_app          :
  a_extended_properties    []: <none>
  a_is_signed                : F

INTERNAL ATTRIBUTES

  i_is_deleted               : F
  i_reference_cnt            : 1
  i_has_folder               : T
  i_folder_id             [0]: 0b00b60380000106
  i_contents_id              : 0000000000000000
  i_cabinet_id               : 0c00b60380000104
  i_antecedent_id            : 1000b60380103960
  i_chronicle_id             : 1000b6038010393b
  i_latest_flag              : T
  i_branch_cnt               : 0
  i_direct_dsc               : F
  i_is_reference             : F
  i_is_replica               : F
  i_vstamp                   : 7

ldallas

Silly questions that you probably already thought of....

1) Does it work and if so what does it do? The 'XYZCustomeMethod' in the entrypoint makes it look like an experiment so I wonder if it is a relic.

2) Is there anything in the either the docbase log or the agent_exec.log from the trace launch?

3) Ordinarily I would have expected to see a "-f something.ebs" identifying the file. If that is not present AND it does something then the script is more than likely in an object somewhere - is it linked to a docapp? part of a workflow or lifecycle action?