|
View previous topic :: View next topic
|
| Author |
Message |
ksubbamanoz
New User
Joined: 16 Sep 2005
Posts: 4
|
|
|
|
| How will a job run a NDM process? what is NDM transmission of files from one mainframe to another? Can NDM process trigger another job in the third party mainframes? |
|
| Back to top |
|
 |
Rupesh.Kothari
Member of the Month
Joined: 27 Apr 2005
Posts: 463
|
|
|
|
HI,
| Quote: |
| what is NDM transmission |
Using NDM you can transfer a file from One mainframe to anothar.
| Quote: |
| Can NDM process trigger another job in the third party mainframes? |
Yes you can trigger a job on another mainframe using NDM strp.
NDM is commonly used for secure and efficient file transfers over different network protocols, such as FTP (File Transfer Protocol) and SFTP (Secure File Transfer Protocol). Here's a detailed explanation of NDM File Transfer:
Overview of NDM File Transfer:
Purpose:
NDM File Transfer is used to move data files between mainframe systems and other systems, such as distributed systems, servers, or cloud platforms.
It facilitates secure, reliable, and efficient data exchange across different network environments.
Features:
Secure Transfers: NDM supports encryption and secure protocols (like SFTP) to ensure data confidentiality and integrity during transfers.
Automation: NDM can be automated using job scheduling tools, allowing scheduled transfers and batch processing of files.
Compression: Files can be compressed before transfer to reduce bandwidth usage and improve transfer speeds.
Error Handling: NDM provides error detection and handling mechanisms to manage transfer failures and ensure data integrity.
Components:
NDM Software: Mainframe systems typically use software like IBM's Connect
(formerly known as NDM or Network Data Mover) for NDM File Transfer.
Connect
Nodes: Nodes represent the endpoints (source and destination) for file transfers. They can be mainframe systems, servers, or other devices.
Configuration: NDM configurations define transfer parameters, security settings, file attributes, and scheduling options.
Workflow:
Define Transfer Parameters: Set up NDM configurations specifying source files, destination directories, transfer protocols, encryption settings, etc.
Initiate Transfer: Start NDM transfers manually or schedule them using job scheduling tools like CA-7, Control-M, or IBM Tivoli Workload Scheduler.
Monitor and Manage: Monitor transfer progress, track transfer logs, and manage transfer queues for efficient data movement.
Advantages:
Efficient Data Movement: NDM optimizes data transfers, reducing latency and improving throughput compared to traditional file transfer methods.
Security: Supports secure protocols and encryption for safe data transmission, critical for sensitive or confidential data.
Automation: Enables automated, scheduled transfers, reducing manual intervention and ensuring timely data exchange.
Use Cases:
Batch Data Transfers: Moving large volumes of data between mainframe and distributed systems in batch processing scenarios.
Backup and Recovery: NDM facilitates backup and recovery processes by transferring data between mainframe and backup servers or storage systems.
Integration with Applications: Integrating mainframe data with cloud applications or third-party systems via automated NDM transfers.
Regards
Rupesh |
|
| Back to top |
|
|
ksubbamanoz
New User
Joined: 16 Sep 2005
Posts: 4
|
|
|
|
| hi can u briefly tell how NDM process works. can u give an example JCL or a program? |
|
| Back to top |
|
|
Kevin
Active User
Joined: 25 Aug 2005
Posts: 234
|
|
|
|
| ksubbamanoz wrote: |
| How will a job run a NDM process? |
You request CONNECT:Direct services in the batch environment through the
Batch Interface program DMBATCH. When you submit a job that contains
the CONNECT:Direct commands as SYSIN input, DMBATCH reads the
input stream and processes the requested functions.
DMBATCH supports all CONNECT:Direct commands.
Your Batch Interface job must meet the following requirements:
- You can't use process statements instream. Use the SUBMIT command with
a pre-existing process that contains the process statements.
- DMBATCH processing of the SUBMIT is asynchronous; the batch job is notified of a
successful SUBMIT, but not whether the COPY itself is executed.
- The first command in the instream must be a SIGNON command.
- Each new CONNECT:Direct command must start on a seperate line. You can
split a command across more than one line using the continuation mark.
Sample job Stream to run the Batch Interface:
| Code: |
//DMBATCH EXEC PGM=DMBATCH,PARM='YYSLYNN'
//STEPLIB DD DISP=SHR,DSN=CD.LINKLIB
//DMPUBLIB DD DISP=SHR,DSN=CD.PROCESS
//DMMSGFIL DD DISP=SHR,DSN=CD.MSG
//DMNETMAP DD DISP=SHR,DSN=CD.NETMAP
//NDMCMDS DD SYSOUT=* <= This is optional
//DMPRINT DD SYSOUT=*
//SYSIN DD DATA
SIGNON USERID=(USERID,PASSWORD)
SUBMIT PROC=PROCESS MAXDELAY=UNLIMITED
SIGNOFF
/*
|
| ksubbamanoz wrote: |
| what is NDM transmission of files from one mainframe to another? |
CONNECT:Direct is a peer-to-peer file-based integration middleware optimized for
assured delivery, high-volume and secure data exchange between enterprises. It moves
files containing any type of data across multiple platforms, multiple file systems, and
different media types.
The major components of CONNECT:Direct OS/390 are:
- Data Transmission Facility (DTF), which executes user commands and processes.
- Application Program Interface (API), which enables user interfaces to communicate
with the DTF.
- User interfaces, such as the Interactive User Interface (IUI), browser end
user interface (EUI), the batch interface (DMBATCH), and the CICS interface.
- Transmission Control Queue (TCQ), which is a VSAM RRDS dataset that stores
processes that are executing, queued for execution, held for retry, or held
for future execution.
| ksubbamanoz wrote: |
| Can NDM process trigger another job in the third party mainframes? |
The CONNECT:Direct process can include many automation options. Some of the
typical ones are:
- RUN JOB. The RUN JOB statement allows a job to be submitted through the JES
Internal Reader. The job must reside in a dataset that is on the node that will
be executing the statement.
- RUN TASK. The RUN TASK statement allows a user program to be executed on the
specified node. The RUN TASK statement is designed so that the process waits until
the task completes before the next process step executes.
- sUBMIT. The SUBMIT statement allows another process to be submitted to either
node.
For more information, please refer to the following documents:
- CONNECT:Direct OS/390 Administration Guide.
- CONNECT:Direct Process Statements Guide.
- CONNECT:Direct OS/390 User's Guide.
all of which are available for licensed customers online at Use [URL] BBCode for External Links, under Customer Support, Support on Demand. |
|
| Back to top |
|
|
mathy
New User
Joined: 02 Mar 2006
Posts: 8
|
|
|
|
Can anyone explain me about the 'SUBMIT PROC' option in DMBATCH control card?  |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| Quote: |
Your batch interface job must meet the following requirements:
- You cannot use process statements in the job stream. Use the SUBMIT command with a preexisting Process that contains process statements.
- The Process you submit resides in the CONNECT:Direct Public Process Library, allocated to the DMPUBLIB DD statement in the DMBATCH JCL. If the Process does not reside in the CONNECT:Direct Public Process Library, use the DSN parameter of the SUBMIT statement to indicate the location of the Process.
|
|
|
| Back to top |
|
|
mathy
New User
Joined: 02 Mar 2006
Posts: 8
|
|
|
|
| Are any standard models available for the process? Because we are having some model processes like MODEL00, MODEL01, NTCMD01,etc. So many options are specified within those processes. I couldn't understand functionality of those processes and purpose of those options. |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
The standard Process models start with the "at" symbol (@):
@COPY
@EIF
@ELSE
@EXIT
@GOTO
@IF
@PROCESS
@RUNJOB
@RUNTASK
@SUBMIT
The equivelent Process models that start with the pound sign (#) are the same, just without the comments.
The entire process is described in detail in the "Connect:Direct OS/390 User's Guide" Chapter 7 (Building, Modifying, and Submitting Processes) in the section titled "Using Statement Models". |
|
| Back to top |
|
|
|
|
  |
All times are GMT + 6 Hours |
|
