OID reference

rConsCommand

1.3.6.1.4.1.597.3.7.1

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.597.3.7 (remoteConsole)
Node code: 1
Node name: rConsCommand
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.597.3.7.1
URN notation: urn:oid:1.3.6.1.4.1.597.3.7.1

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 597 3 7 1}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) comtek(597) comtekos400Mib(3) remoteConsole(7) rConsCommand(1)}

OID-IRI notation

/1/3/6/1/4/1/597/3/7/1
/ISO/Identified-Organization/6/1/4/1/597/3/7/1
/ISO/3/6/1/4/1/597/3/7/1

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/identified-organization/dod/internet/private/enterprises/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/identified-organization/dod/internet/private/ldap-enterprise/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/identified-organization/dod/internet/private/vendor-objects/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/org/dod/internet/private/enterprise/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/org/dod/internet/private/enterprises/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/org/dod/internet/private/ldap-enterprise/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/org/dod/internet/private/vendor-objects/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/iso-identified-organization/dod/internet/private/enterprise/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/iso-identified-organization/dod/internet/private/enterprises/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/iso-identified-organization/dod/internet/private/ldap-enterprise/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/iso-identified-organization/dod/internet/private/vendor-objects/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/iso-organization/dod/internet/private/enterprise/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/iso-organization/dod/internet/private/enterprises/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/iso-organization/dod/internet/private/ldap-enterprise/comtek/comtekos400Mib/remoteConsole/rConsCommand
/iso/iso-organization/dod/internet/private/vendor-objects/comtek/comtekos400Mib/remoteConsole/rConsCommand

SNMP properties

Value type: DisplayString
Maximum access defined by MIB: read-write
Status in MIB: mandatory

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Published definition

The displayed source records contain one distinct definition. Compare its source records.

rConsCommand OBJECT-TYPE
     SYNTAX DisplayString
     ACCESS read-write
     STATUS mandatory
     DESCRIPTION "The remote console command to be executed on the AS/400.
          This feature permits the user to select if the output of
          the command is to be captured and converted into a series
          of userMsg traps. A remote console command has the format:

                CMD<xxx> OUT<yyy> TAG<zzz>

          where xxx is the OS/400 command to be executed, yyy is the name
          of the file that the OS/400 command generates for print output,
          and zzz is a user selected alphanumeric string which is to
          appear in each userMsg trap that is generated. For example,

                CMD<WRKACTJOB OUTPUT(*PRINT)> OUT<QPDSPAJB> TAG<actJobs>

          If the results of the command are not to be sent as userMsg
          traps, both the OUT and TAG fields should be omitted.

          The OUT field is required if the print file produced by the
          command is to be sent as a series of userMsg traps to the
          SNMP manager. When using the OUT field, it is required that
          the CMD field include OUTPUT(*PRINT) to direct the output
          of the command to a file. The name that should be specified
          for the OUT field is dependent on the output file that is
          generated by the specified OS/400 command.

          The TAG field is intended to assist the user in distinguishing
          userMsg traps that are generated by multiple remote console
          commands. The TAG field is optional. "
     ::= { remoteConsole 1 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

The remote console command to be executed on the AS/400. This feature permits the user to select if the output of the command is to be captured and converted into a series of userMsg traps. A remote console command has the format: CMD<xxx> OUT<yyy> TAG<zzz> where xxx is the OS/400 command to be executed, yyy is the name of the file that the OS/400 command generates for print output, and zzz is a user selected alphanumeric string which is to appear in each userMsg trap that is generated. For example, CMD<WRKACTJOB OUTPUT(*PRINT)> OUT<QPDSPAJB> TAG<actJobs> If the results of the command are not to be sent as userMsg traps, both the OUT and TAG fields should be omitted. The OUT field is required if the print file produced by the command is to be sent as a series of userMsg traps to the SNMP manager. When using the OUT field, it is required that the CMD field include OUTPUT(*PRINT) to direct the output of the command to a file. The name that should be specified for the OUT field is dependent on the output file that is generated by the specified OS/400 command. The TAG field is intended to assist the user in distinguishing userMsg traps that are generated by multiple remote console commands. The TAG field is optional.

Sources for this description

COMTEK official NMServer AS/400 MIB

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1COMTEK official NMServer AS/400 MIB1 record · 1 source

Description 1

rConsCommand · mandatoryCOMTEK official NMServer AS/400 MIB1 source

Status in source: mandatory.

Names: rConsCommand

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rConsCommand",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The remote console command to be executed on the AS/400. This feature permits the user to select if the output of the command is to be captured and converted into a series of userMsg traps. A remote console command has the format: CMD<xxx> OUT<yyy> TAG<zzz> where xxx is the OS/400 command to be executed, yyy is the name of the file that the OS/400 command generates for print output, and zzz is a user selected alphanumeric string which is to appear in each userMsg trap that is generated. For example, CMD<WRKACTJOB OUTPUT(*PRINT)> OUT<QPDSPAJB> TAG<actJobs> If the results of the command are not to be sent as userMsg traps, both the OUT and TAG fields should be omitted. The OUT field is required if the print file produced by the command is to be sent as a series of userMsg traps to the SNMP manager. When using the OUT field, it is required that the CMD field include OUTPUT(*PRINT) to direct the output of the command to a file. The name that should be specified for the OUT field is dependent on the output file that is generated by the specified OS/400 command. The TAG field is intended to assist the user in distinguishing userMsg traps that are generated by multiple remote console commands. The TAG field is optional. \"",
    "::=",
    "{",
    "remoteConsole",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "DisplayString"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The remote console command to be executed on the AS/400. This feature permits the user to select if the output of the command is to be captured and converted into a series of userMsg traps. A remote console command has the format: CMD<xxx> OUT<yyy> TAG<zzz> where xxx is the OS/400 command to be executed, yyy is the name of the file that the OS/400 command generates for print output, and zzz is a user selected alphanumeric string which is to appear in each userMsg trap that is generated. For example, CMD<WRKACTJOB OUTPUT(*PRINT)> OUT<QPDSPAJB> TAG<actJobs> If the results of the command are not to be sent as userMsg traps, both the OUT and TAG fields should be omitted. The OUT field is required if the print file produced by the command is to be sent as a series of userMsg traps to the SNMP manager. When using the OUT field, it is required that the CMD field include OUTPUT(*PRINT) to direct the output of the command to a file. The name that should be specified for the OUT field is dependent on the output file that is generated by the specified OS/400 command. The TAG field is intended to assist the user in distinguishing userMsg traps that are generated by multiple remote console commands. The TAG field is optional."
    ],
    null,
    null,
    null,
    null
  ]
}

COMTEK official NMServer AS/400 MIB
Module: COMTEKA4-MIB

See published definition above
Module imports
```
{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'RFC1155-SMI': ['enterprises'], 'RFC1213-MIB': ['DisplayString']}
```
Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.
Source data warning: This historical COMTEK AS/400 MIB is extracted from the publisher’s 2006 PDF. The complete MIB has invalid lowercase type declarations; individual assignments are recovered and the unchanged original PDF is available for verification. Actual implementation and compatibility with current systems are not established.
· Download COMTEKA4-MIB — text extracted from the official PDF
Related source files and packages:
- COMTEK — original NMServer for AS/400 MIB PDF

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.597)

Harris Steve