Just by doing one file transfer you dont have to worry about getting UNIX system documentation and trying to find out what happened. Can anyone please help me out by letting me know of some documents which i can have a glance at? One more thing, I am completely new to the UNIX system. You need to look at the NDM log or take the NDM process number and check the statistics of the file transfer.Īlso you can go to Unix box, and see the NDM log whether the file arrived on the Unix box. JCL MAXCC=0 doesnt make sense in case of NDM transfers. Also, many of the same users had accounts on multiple systems. Is it possible that the intended unix system is not where the transfer is being sent? Once upon a time, i worked in an environment where there were several unix servers and they had very similar names and ip addresses. Has anyone searched the unix file system for any file named CARRTST.DAT (the "new" path/file may have gotten hung off of other than the root directory)? If this is a file name already used in multiple places, change the file name to something that cannot already exist and try again. ![]() But when I tried to locate the file in the UNIX server, I was not able to find the same there. One more thing, the job ran successfully and ended with MAXCC=0. If you are overriding this parameters, then you should have continuation chars. Entries beginning in column 1 areĬan any one please help me out to remove the error. Ensure that the command keyword isĮntered after column 1. LONG TEXT => The requested command is not supported by C:D. SHORT TEXT => SCIA001I Invalid C:D command. SHORT TEXT => SSPA001I Submit process successful SCIB009I SUBMITTED PROCESS NUMBER 00038370 SCIB007I COMMAND => SUBMIT PROC=MODEL90 SNODE= HOLD=NO CASE=YES SHORT TEXT => SAFA000I Connect:Direct SIGNON process completed. SIGNON COMMAND (CONDENSED) => USERID /NODE = N48FF9 When i checked in the spool, I found the following error message: &OUT01='/DATASTAGE/DATA/CLSI_REQMNT/LOSSDB/CARRTST.DAT'-īut using the above, I am getting a return code of 8. SUBMIT PROC=MODEL90 SNODE= HOLD=NO CASE=YES. ![]() For that purpose, its essential to use the Connect Direct Method of file transfer. I am required to transfer a file from mainframe database to Unix database. PowerPath, because of the missing enhancement, will only display the spoofed information (as in "inq -no_dots" below).Connect Direct to transfer a file from mainframe to Unix -IBM MainframesĬonnect Direct to transfer a file from mainframe to Unix that you can only see with the "-native" option. The paths remain identical (and this is why the NDM is transparent for the host) although they point to different devices. Here, devices 57B, 663 and 6AE from array xx05 were migrated to devices 03F, 040 and 041 on array xx90. With the "-native" option, this utilities allows you to see the non-spoofed information.Į.g. It can be download from (username : anonymous password: your E-Mail address). Solaris)įor hosts which do not benefit from this enhancement, the "inq" utility can be used. Although the device WWN is unchanged, it now represents LUN 39DD from VMAX xxx0863.Ĭase 2 : Hosts where the enhancement is not supported (e.g. The source of the migration is here LUN 2237 on VMAX xx0879ĭuring the migration, both arrays, both LUN id and all the relevant FA and paths are visible :Īfter the migration, only the v3 information is displayed. As of November 7th 2017, this enhancement is not planned for Solaris and alternate methods need to be used to find the true identity of a device.Ĭase 1 : with PowerPath 6.2 and above for AIX, Linux and Windows:īefore the NDM, only the v2 information is visible. This feature is available for Linux, AIX and Windows. Starting with PowerPath 6.2, "powermt display dev=XX" is displaying the real array S/N, the real LUN number and the real FA number (non spoofed information). ![]() ![]() As a consequence, the WWN of the device has to remain identical before and after the NDM. The purpose of an NDM is to be transparent to the host.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |