mainframe

“COPY” statement with “REPLACING” in COBOL

笑着哭i 提交于 2019-12-05 00:07:59
问题 I am getting compilation error as, A "COPY" statement with "REPLACING" phrase was found within a nested "COPY". This is our compilation setting that we can not use REPLACING verb in nested copy. We have one copybook which is having multiple copy statements with replacing verb. Can anyone help me to resolve this error? 回答1: Nesting COPYBOOKS in COBOL is a bit of a trick. In general you may nest copybooks only if they do not contain the REPLACING phrase and do not cause recursion. Suppose you

DB2 database in Oracle SQL developer

≯℡__Kan透↙ 提交于 2019-12-04 09:17:45
问题 I've heard it's possible to connect to a mainframe DB2 database with a client like Oracle SQL developer. I've looked on-line and can't seem to find the connector files needed to do this in SQL developer. Can anyone direct me to a link to make this work? Or tell me if im just looking for the wrong thing to begin with. I've got the connector working with MySQL databases in Oracle, so I assumed it would be similar for a DB2 database. 回答1: The easiest way to connect to DB2 is through their JDBC

How can I convince z/OS scp to transfer binary files?

人走茶凉 提交于 2019-12-04 09:11:39
We have SSH-based file transfer scripts currently set up for Linux-to-Linux and we're porting them to z/OS to go z/OS-to-Linux. Note that this is with USS, the UNIX system services within z/OS otherwise known as OMVS, which uses EBCDIC under the covers, not zLinux which uses ASCII. We've set up all the SSH key files and what-not, and the transfer itself is working fine. However z/OS, in it's infinite wisdom, insists on converting the files from EBCDIC to ASCII despite the fact that they're binary files - this is screwing up the content of the destination files. The scp manpage on z/OS states:

“COPY” statement with “REPLACING” in COBOL

久未见 提交于 2019-12-03 16:04:58
I am getting compilation error as, A "COPY" statement with "REPLACING" phrase was found within a nested "COPY". This is our compilation setting that we can not use REPLACING verb in nested copy. We have one copybook which is having multiple copy statements with replacing verb. Can anyone help me to resolve this error? Nesting COPYBOOKS in COBOL is a bit of a trick. In general you may nest copybooks only if they do not contain the REPLACING phrase and do not cause recursion. Suppose you had the following two copybooks: COPYBOOK ABC 01 :A:-VAR-A1 PIC X. 01 :A:-VAR-A2 PIC X. COPY XYZ REPLACING ==

How to use the C socket API in C++ on z/OS

Deadly 提交于 2019-12-03 06:26:36
问题 I'm having issues getting the C sockets API to work properly in C++ on z/OS . Although I am including sys/socket.h , I still get compile time errors telling me that AF_INET is not defined. Am I missing something obvious, or is this related to the fact that being on z/OS makes my problems much more complicated? Update : Upon further investigation, I discovered that there is an #ifdef that I'm hitting. Apparently z/OS isn't happy unless I define which "type" of sockets I'm using with: #define

equivalent of ftp put and append in scp

时间秒杀一切 提交于 2019-12-03 05:40:19
I have a legacy script which I am not able to understand. The script is to transfer 4 files (2 ebcdic format files and 2 pdf files) in unix to mainframes through ftp. ebcdic format file 1 is abc.xyz ebcdic format file 2 is pqr.xyz pdf file 1 is abc.pdf pdf file 2 is pqr.pdf mainframe file name is AM2P.BJCUN.SALCHG The syntax of the command in the script is as below: quote site recfm=fb put /myfiles/abc.xyz AM2P.BJCUN.SALCHG append /myfiles/abc.pdf AM2P.BJCUN.SALCHG append /myfiles/pqr.xyz AM2P.BJCUN.SALCHG append /myfiles/pqr.pdf AM2P.BJCUN.SALCHG I want to achieve the same thing through SCP.

teaching my self Z/OS assembler?

吃可爱长大的小学妹 提交于 2019-12-02 21:09:42
'I've interned at a company that does a lot of mainframe work. Most of my mainframe experience has been using Java and Unix System Services. I've had some experience with the ISPF interface and C but none with assembler. I’m graduating shortly and will be taking an independent study my last semester. I’d like to stick with the mainframe and was wondering what resources could teach me mainframe assembler? Note I don’t have experience writing assembler for any platform but do understand binary, hex, and have a theoretical understanding of registers. None of the following are tutorial-like, just

Unpacking COMP-3 digit using Record Editor/Jrecord

十年热恋 提交于 2019-12-02 20:47:39
问题 I have created layout based on cobol copybook. Layout snap-shot: I tried to load data also selecting same layout, it gives me wrong result for some columns. I try using all binary numeric type. CLASS-ORDER-EDGE DIV-NO-EDG OFFICE-NO-EDG REG-AREA-NO-EDG CITY-NO-EDG COUNTY-NO-EDG BILS-COUNT-EDG REV-AMOUNT-EDG USAGE-QTY-EDG GAS-CCF-EDG result snapshot Input file can be find below attachment enter link description here or https://drive.google.com/open?id=0B-whK3DXBRIGa0I0aE5SUHdMTDg Expected

Unpacking COMP-3 digit using Record Editor/Jrecord

可紊 提交于 2019-12-02 11:52:09
I have created layout based on cobol copybook. Layout snap-shot: I tried to load data also selecting same layout, it gives me wrong result for some columns. I try using all binary numeric type. CLASS-ORDER-EDGE DIV-NO-EDG OFFICE-NO-EDG REG-AREA-NO-EDG CITY-NO-EDG COUNTY-NO-EDG BILS-COUNT-EDG REV-AMOUNT-EDG USAGE-QTY-EDG GAS-CCF-EDG result snapshot Input file can be find below attachment enter link description here or https://drive.google.com/open?id=0B-whK3DXBRIGa0I0aE5SUHdMTDg Expected output: Related thread Unpacking COMP-3 digit using Java First Problem you have done an EBCDIC --> ascii

Connect Direct : File sending from Mainframe to Unix

99封情书 提交于 2019-12-02 10:32:50
When I am sending a Variable length file from Mainframe Connect direct to UNIX box, the file on UNIX have some extra bytes on the beginning of the Mainframe file, I tried using different SYSOPTS option but I am still getting those intial bytes. Any Idea ? You should look at getting the file copied to a Fixed-Length record (recfm=FB) file on the mainframe before doing the transfer. There are a number of mainframe utilities that can do this (i.e. sort). If you transfer it as a VB file you should also leave it as an EBCDIC file (the BDW/RDW fields are binary fields and should not be translated to