Bulk Data Movement Guide

10.5
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

Setting Up a Netport Job for IDMS Bulk Data Movement

If the SECURITY statement in the DBMOVER configuration member is set to 2, you must use a netport job to run an IDMS bulk data movement job. A SECURITY setting of 2 requires your z/OS security management system, for example, RACF, to verify the logon user ID of each user application that attempts to access IDMS data.

To set up a netport job for access to an IDMS data source, use the sample netport job in the TAPEJCL member of the RUNLIB library as a template.

To set up a netport job for IDMS bulk data movement:

Copy the TAPEJCL member to create a basis for the IDMS netport job.

If you are not using the z/OS PC services routine, verify that the PowerExchange copies of the IDMS load libraries, hlq
.IDMS.LOADLIB and hlq
.IDMS.DBA.LOADLIB, are specified in the STEPLIB DD statement of the netport JCL.

Add the following DD statement to the IDMS netport job:

//SYSIDMS    DD DSN=&HLQ..RUNLIB(DTLDMCL),
//             DISP=(SHR)

Verify that the relevant SYSCTL statement is included in the netport JCL if you are running an IDMS Central Version, or verify that the following DD statements are included in the netport job if you are running IDMS in Local mode:

//IDMSDCT    INCLUDE MEMBER=IDMSDICT
//IDMSFIL    INCLUDE MEMBER=IDMSFILE

The IDMSDICT and IDMSFILE members require the relevant dictionary definitions and database file definitions.

In the DBMOVER configuration member, edit the LISTENER and NETPORT statements that are supplied for TAPEJCL. In each statement, enter a valid port number for the netport job. In the NETPORT statement, assign the netport job member to the specified port.

If you want to run a database row test from the PowerExchange Navigator to read IDMS data, also add a NODE statement to the dbmover.cfg on the system where the PowerExchange Navigator runs, for example:

NODE=(idmsnet,TCPIP,ipaddress_or_hostname,port_number)

Edit other statements, as needed.

If you are using the z/OS PC services routine, specify

PC_AUTH=Y

in the DBMOVER configuration member that the netport job uses. Also add a DTLLOAD DD statement to the netport job that points to the system IDMS load libraries, not to the PowerExchange copies of these libraries.

Restart the PowerExchange Listener so that PowerExchange detects the netport job.

Rename Saved Search

Table of Contents

Bulk Data Movement Guide

Bulk Data Movement Guide

Setting Up a Netport Job for IDMS Bulk Data Movement

Setting Up a Netport Job for IDMS Bulk Data Movement