Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Utilities
  3. createdatamaps - Data Map Creation Utility
  4. DTLCCADW - Adabas PCAT Utility
  5. DTLCUIML - IMS Log Marker Utility
  6. DTLINFO - Release Information Utility
  7. DTLREXE - Remote Execution Utility
  8. DTLUAPPL - Restart Token Utility
  9. DTLUCBRG - Batch Registration Utility
  10. DTLUCDEP - CDEP Maintenance Utility
  11. DTLUCSR2 - IDMS SR2 and SR3 Records Utility
  12. DTLUCUDB - DB2 for Linux, UNIX, and Windows CDC Utility
  13. DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities
  14. DTLURDMO - Data Map Utility
  15. DTLUTSK - Task Control Utility
  16. EDMLUCTR - Log Scan and Print Utility
  17. EDMUOPTS - Service Aid Utility
  18. EDMXLUTL - Event Marker Utility
  19. HOSTENT - TCP/IP Address Reporter Utility
  20. PWXCATMY - MySQL Catalog Utility
  21. PWXUCCLPRT - Print Log Summary Utility
  22. PWXUCDCT - Logger for Linux, UNIX, and Windows Utility
  23. PWXUCREG - Capture Registration Suspend Utility
  24. PWXUCRGP - Capture Registrations Print Utility
  25. PWXUDMX - Data Maps Update Time ECSA Memory Utility
  26. PWXUGSK - SSL Reporting Utility for z/OS
  27. PWXUMAP - Map List Utility
  28. PWXUSSL - PowerExchange SSL Reporting Utility

SUBMIT Statement

SUBMIT Statement

Use DTLREXE SUBMIT to submit a job to a remote z/OS platform or server.
You can enter SUBMIT parameters at the command line. Alternatively, you can use the
cs
parameter to point to a parameter file that contains the parameters you need.
dtlrexe cs=<
parameter_file
>
SUBMIT has the following parameters:
loc
Required. The location of the PowerExchange Listener, as defined in a NODE statement in the DBMOVER configuration file.
prog
Required. This value must be to SUBMIT.
config
Optional. The DBMOVER configuration file that you want the DTLREXE utility to use, when you do not want to use the default DBMOVER file or the DBMOVER file that is set in the PWX_CONFIG environment variable. This parameter is used only when you run DTLREXE on Linux, UNIX, and Windows. This parameter is ignored on IBM i or z/OS.
fn
Optional. The name of the file on z/OS that contains the JCL to be submitted, including the job name. Use the following format:
fn=”dtlusr.jcl(
yourjob
)”
On Windows, use the following format:
fn=\”dtlusr.jcl(
yourjob
)\”
mode
Optional. Specifies the submit mode. Use the following format:
mode=(job|task},{wait|nowait|timed)
The available modes are:
  • job
    . A submitted job
  • task
    . A started task. (Not currently supported.)
  • wait
    . Synchronous. Report result at the end and wait for completion.
  • nowait
    . Asynchronous. Submit the job but do not wait until report completion.
  • timed
    . Synchronous. Waits for the length of time that is specified by the time parameter.
output
Optional. The file name for the file that contains the results from the job. Use the following format:
output=dtlusr.output
If the output is a PDS member, the same format requirements are in place as for the
fn
parameter.
{pwd|epwd}
Optional. A password or encrypted password for the specified user ID. For a location on i5/OS or z/OS, you can enter a passphrase or encrypted passphrase instead.
  • pwd
    . A clear text password for the specified user, which allows access to the target. If a password contains nonalphanumeric characters, it must be enclosed in double quotation marks (“). A password cannot contain embedded double quotation marks.
    For access to an i5/Os or z/OS location, you can enter a valid PowerExchange passphrase instead of password. An i5/OS passphrase can be from 9 to 31 characters in length. A z/OS passphrase can be from 9 to 128 characters in length. A passphrase can contain the following characters:
    • Uppercase and lowercase letters
    • The numbers 0 to 9
    • Spaces
    • The following special characters:
      ’ - ; # \ , . / ! % & * ( ) _ + { } : @ | < > ?
      The first character is an apostrophe.
    Passphrases cannot include single quotation marks (‘), double quotation marks (“), or currency symbols.
    If a passphrase contains spaces, you must enclose it with double-quotation marks ("), for example,
    "This is a passphrase"
    . If a passphrase contains special characters, you must enclose it with triple double-quotation characters ("""), for example,
    """This passphrase contains special characters ! % & *."""
    . If a passphrase contains only alphanumeric characters without spaces, you can enter it without delimiters.
    To use passphrases, ensure that the PowerExchange Listener runs with a security setting of SECURITY=(1,N) or higher in the DBMOVER configuration member. On z/OS, the DTLCFG DD statement in the DTLREXE JCL points to the DBMOVER member. On i5/OS, the DBMOVER member is the CFG file in the PowerExchange
    datalib
    library. For more information, see "SECURITY Statement" in the
    PowerExchange Reference Manual
    .
    On z/OS, a valid RACF passphrase can be up to 100 characters in length. PowerExchange truncates passphrases longer than 100 characters when passing them to RACF for validation.
  • epwd
    . An encrypted password for the specified user.
    For access to an i5/OS or z/OS location, you can enter an encrypted PowerExchange passphrase instead of an encrypted password. Do not encrypt a passphrase that contains invalid characters, such as double-quotation marks, single quotation marks, or currency symbols.
    You can use the PowerExchange Navigator to encrypt a password or passphrase.
result
Optional. The file to which the results from the job are written on the client platform where DTLREXE runs.
The file specification must be suitable for the platform.
If the output is a PDS member, the same format requirements are in place as for the
fn
parameter.
submittimeout
Optional. The time, in seconds, to wait for the submitted job to start running.
time
Optional. The time, in seconds, to wait for the job to return results. This wait period starts when the job is submitted.
uid
Optional. A user ID that allows access to the specified location. If you specify a user ID, you must also enter a
pwd
or
epwd
value, but do not enter both.
For a location on a supported Linux, UNIX, or Windows system, if you have enabled PowerExchange LDAP user authentication, the user ID is the enterprise user name. For more information, see the
PowerExchange Reference Manual
.

0 COMMENTS

We’d like to hear from you!