Ensuring that UNIX User IDs are Set Up - Parallel Transporter

Teradata Parallel Transporter Reference

Product
Parallel Transporter
Release Number
16.10
Published
July 2017
Language
English (United States)
Last Update
2018-06-28
dita:mapPath
egk1499705348414.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2436
lifecycle
previous
Product Category
Teradata Tools and Utilities

This task is performed by the system security staff or system programmers.

Teradata PT requires that User OMVS Segments are defined.

  • The userId must be correctly set up for USS (UNIX) access. In MVS terms, this is called adding an OMVS segment with a valid (UID/GID) and (home dir).

    If the OMVS segment is not defined, the results are undetermined.

    Teradata PT hangs when the default OMVS Segment is used because IBM (when running the default OMVS segment) does not support some of the callable services used by Teradata PT, among them kill(), pidaffinity(), trace(), and sigqueue().

  • The userId must have correct RACF/ACF2/Top Secret security authorizations to the DBMS and the database in question.