links: コピーブランド スーパーコピー 財布 スーパーコピーブランド ブランド コピー 時計 スーパーコピー ブランドコピー激安

Mainframe PC communication using TSO C/S WSA – remarks

CONTENTS:

Bottom

Remark 1. Complicated operations compared to IND$FILE or FTP file transfer

Remark 2. The function “Upload of full library”  doesn’t exist

Remark 3. TSO split screens are  possible only in native mode

Remark 4. WSA (PC-client) session has “short delay time”

Remark 5.  Download/upload of load library member in text mode

*** Remarks 1, 3 and 4  are  updated!

When using IBM TSO C/S WSA  communication functions in z/OS  some  remarks may be  given below :

 

            Remark 1. Complicated operations compared to IND$FILE or FTP file transfer

The operations before starting  transfer (establishing  client – server connection) are  complicated  and take a certain time.

First it is necessary to Click  on WSA.exe (only once during PC running) in PC directory (where WSA  application client agent is installed according the C/S  WSA instructions with the “Auto connect list” setting in System Register options) so that WSA agent become active with “0 session(s) are active”).

After logon in TSO/ISPF   on command line of  “ISPF  Primary Option Menu” (P) it is necessary to enter WSCON (only once during this TSO logon). The panelInitiate Workstation Connectionappears with all prepared settings  according the C/S WSA instructions  and should be filled up if it is the first time or  if  IP address is changed.

After pressing Enter, small “Connection” window appears on the screen requring  answer Yes to Accept connection. You ought to Click the  button Yes  (to have “1 session(s) are active”) and return again on ” TSO/ISPF Primary Option Menu* (P) to see if the message “Connected” appears on the right upper corner of the screen. Then you can enter   3.7.2 on command line  and the “Download/Upload Data Set To/From Workstation” panel will be displayed where it is necessary to insert  the following information for downloading  object member CIFTEST  from z/OS object library BCI05.LIB.BASE.OBJECT as  PC file d:\ciftest.obj in binary mode:

On  “Other Partitioned or Sequential Data Set:

Data Set Name . . .”     enter:  ‘BCI05.LIB.BASE.OBJECT(CIFTEST)’

***If  you miss to put DSN in ‘   ’    the message “Data set not cataloged” appears.

On “ Workstation File:

File Name . . . . . “ enter: d:\ciftest.obj

On “Transfer Option                                                  Options “          enter:

1  1. Download to workstation            Generate statistics on upload

2. Upload from workstation                      Transfer in text mode

/  Replace existing member/file 

If in    “Data Set Name . . .”   is   entered only the library  :  ‘BCI05.LIB.BASE.OBJECT after pressing  Enter  the panel MEMBER LIST  BCI05.LIB.BASE.OBJECT will  appear.  Then you have to chose the member CIFTEST  with S (select)    and press Enter   – Transfer completed will appear   on  the right upper end of the screen and *XFER  under Prompt.  At this moment the transfer is completed.

The object member  CIFTEST  from library    BCI05.LIB.BASE.OBJECT is received on PC  in binary format as PC file  d:\ ciftest.obj and can be opened with UltraEdit in EBCDIC edit mode.

The same result with IND$FILE:

After TSO logon and P.6 menue active  in” a” session from PC Command Prompt    enter:

receive d:ciftesto.obj  a:BCI05.lib.base.object(ciftest)

(This is shown and operations can be compared  for TSO/IND$FILE and TSO/ISPF  C/S WSA  in   article   Mainframe  Program relocation” of site Mainframetips.com with link  http://www.mainframetips.com/mainframe-program-relocation/#m_2_2   – “Receiving  the object  member  from Mainframe on   PC in binary    format and sending  to remote Mainframe with PC connected”  ).

The same result with FTP and  no TSO logon:

From PC   start  prepared FTP.bat(ftp-s:d\ftp.txt>d:ftpmch.err) and  prepared

ftp.txt:

Open 10.212.5.91

IBMUSER

IBMUSER

cd..””

binary

get BCI05.lib.base.object(ciftest) d: d:ciftesto.obj

disconnect

quit

 

            Remark 2.  The function “Upload of full library”  doesn’t exist

The Upload of full library function doesn’t work   (only one member from the downloaded library can be uploaded). (Maybe there is a way to perform this function which is not known to   the Author.)

-The downloading  source library in text/charcter mode   is OK.

– The downloading  object library in binary mode  is OK.

– The downloading  load  library in binary or text  mode  is OK.

But if you want to upload full (or more members) of   source, object or load  library it is  not possible. A trial is made to upload  in Mainframe object library  ‘BCI05.LIB.BASE.OBJECT.IBAN’ all the members of the PC object library d:\ciftesto\*.bin  downloaded successfully as follows in “Download/Upload Data Set To/From Workstation” panel:

Other Partitioned or Sequential Data Set:

Data Set Name . . . ‘BCI05.LIB.BASE.OBJECT.IBAN’

Volume Serial . . .         (If not cataloged)

Workstation File:

File Name . . . . . d:\ciftesto\*.bin

Transfer Option                       Options

 2  1. Download to workstation            Generate statistics on upload

     2. Upload from workstation            Transfer in text mode

/  Replace existing member/file

The answer is:

The target of the upload must be a specific member of a PDS or a sequential

data set.

This function (download and upload of full library) is very important because of   the following reasons:

–  When it is necessary  fast full library relocation to another Mainframe   via Internet  or  with portable PC storage media (as it is explained in  article   Mainframe  Program relocation” of site Mainframetips.com with link  http://www.mainframetips.com/mainframe-program-relocation/#m_1_3   for item 1.3.  Relocation of full source library between local and remote Mainframe  via PC)

– For saving Mainframe full libraries on the  PC enormous and modern storages with subsequent  very fast restore (upload to Mainframe).

            Remark 3. TSO split screens are   possible only in native mode

It is    possible to have split screens in one TSO session and   this  is a big advantage!

You can  switch with  PF9 the split screens  signing on TSO only once.  Almost always TSO user works with two screens – to follow the job executions or file transfers and the files or libraries members contents.

 

            Remark 4.WSA (PC-client) session has  “short delay time”

WSA (PC-server) session has  “short delay time” if the TSO session is closed incidentally (power failure, automatically if long time TSO is inoperative, closed session  without TSO logoff). The communication Client/Server  stops  but still “1 session(s) are active” and each time  after WSCON it’s necessary  to start another session without able  to delete  the previous.   The small “Connection” window will appear on the screen requiring  answer Yes to Accept connection. You ought to Click again  the  button Yes  (WSA has now “2 session(s) are active”) and return to ”TSO/ISPF Primary Option Menu* (P) to see if the message “Connected” appears on the right upper corner of the screen. Then you can enter   3.7.2 on command line  and the “Download/Upload Data Set To/From Workstation” panel will be displayed where it is necessary to insert  the information for downloading/uploading   the member  from/to  z/OS library to/from  PC .

To get rid of this problem you need to close WSA agent on PC and start again WSA.exe.

Always use regular WSDISC or TSO logoff after finishing work with TSO C/S WSA!

 

            Remark 5.  Download/upload of load library member in “text mode

 

One load module (load library member) can’t  be downloaded and uploaded in binary  mode successfully because the next step of Linkedit finish with cc=0012 and the execution of the produced load module is not successful. This is truth also for IND$FILE and FTP file transfer.

The   load module (load library member)  can  be  downloaded and uploaded only in text mode and  then the next step of Linkedit finish with cc=0000 (which is good)  and the execution of the produced load module is successful.  This is truth also for IND$FILE and FTP file transfer.

The question is why this happens  (succesfull in text/character mode)  instead of binary as should be?   The same peculiarity is observed  in  article   Mainframe  Program relocation” of site Mainframetips.com with links http://www.mainframetips.com/mainframe-program-relocation/#m_3_2  to   “3.2.  Receiving  the load   member  from Mainframe on   PC  and sending  to remote Mainframe with PC connected” and  http://www.mainframetips.com/mainframe-program-relocation/#m_3_3   to        “Relocation of full  load  library between local and remote Mainframe  via PC ”  where full load library is uploaded OK.

End

Incoming search terms:

  • download file from mainframe to pc

Leave A Reply

Comments

No comments yet, be the first to add one!

Places

 

Choose donation amount:
您要找的资源已被删除、已更名或暂时不可用。 Clef two-factor authentication