Description

Use the pdls command to request that InfoPrint display selected attribute values for one or more jobs or other InfoPrint objects.

  • By default, InfoPrint creates a filter when listing jobs that only lets you see your jobs. The jobs have a predefined value for the filter that is equal to the job attribute user-name; this value is your login identity when you submit a job. You can add to this filter to further restrict the jobs for which InfoPrint returns information.
  • You must suppress the default filter by using the -U flag or turn off all filtering with the -F flag to see more than your own jobs.
  • If you only specify the ServerName as the command argument, InfoPrint displays the attribute values for all objects belonging to the object class you specify.
  • In general, you can only list the attributes of the object class you are requesting. However, you can view attributes of intial-value-jobs (IVJs) and inital-value-documents (IVDs) associated with a logical destination through the logical destination.
  • The all-device option on the -r flag can only be used with actual destinations that have snmp-active specified as true.
  • If SNMP is enabled on an actual destination, you can also be able to query information directly from the device associated with the actual destination by querying for device attributes. See “Setting up SNMP” in the RICOH InfoPrint Manager for AIX: Procedures, RICOH InfoPrint Manager for Linux: Procedures, or RICOH InfoPrint Manager for Windows: Procedures.
  • The contents and the order of the information returned from queries of device attributes can vary between queries and between devices.
  • The results returned from queries of device attributes will not be translated.
  • You can list the attribute values for specific jobs by using the local ID or the global ID. You must have submitted the job to use the local ID.
      Note:
    1. There is a situation when you must use the global ID. If the InfoPrint communications daemon responsible for the mapping of local ID-to-global ID values is not available, this can prevent InfoPrint from tying the local ID to the global ID. If this situation exists, you must use the global ID, the name of the server, or an argument specification using global characters.
    2. There is a possible situation that can occur if your administrator has set the PDIDTABLE environment variable to a low value, for example 10. You submit a series of jobs during a short time span such that the number of jobs you have in process is larger than the value set, say 14. You will have two jobs with the local IDs of 1, 2, 3, and 4. However, InfoPrint no longer associates the first four jobs with a local ID because those local IDs now belong to the 11th, 12th, 13th, and 14th jobs. Therefore, you must use the global ID to take action on any of the first four jobs.
    3. If the PDIDTABLE environment variable is set to 0, jobs cannot be referenced by the local IDs.

Parent topic: pdls command: lists selected attribute values