What is the proper way to copy z/OS load modules?

Windows, and to some extent, Linux have made IT professional forget a time when operating systems were recorded oriented, like MVS or z/OS, or VMS. In record oriented operating systems, the OS knows what the data structure is inside files managed by it. This knowledge makes record processing very powerful and efficient.

In Linux and Windows, all files are just streams of bytes. Only the New Line and CRLF special characters tell editors that a text file has lines of variable lengths, but to the OS text files or binaries are all just streams of bytes.

So when people need to copy z/OS load modules (ie binaries), they often forget that all datasets (including load modules) have a record structure and a blocking factor which needs to be kept when copying load modules.

In this video I show how to properly copy load modules in z/OS. Hopefully this helps to clear the fog on this issue, especially for newcomers.

For more how-tos relating to the mainframe world and to Hercules, visit my Youtube channel. 

thanks

Moshix

Comments

  1. UnknownNovember 5, 2018 at 1:48 AM

    Nice and good article. It is very useful for me to learn and understand easily. Thanks for sharing your valuable information and time. Please keep updatingmulesoft online training Hyderabad

    ReplyDelete

Post a Comment

Popular posts from this blog

Get a JES3 Complex Up and Running

Image
UPDATE: January 19, 2019 The procedures here work for me and hundreds of others repeatedly and I have made a video about all this which you can find on Youtube here : Prerequisites 1. Hercules 3.12/Spinhawk/4.00(hyperion) with Peter Jansen's CTC extensions I use the Hercules as provied by the latest version of Juergen Winkelmann's amazing MVS 3.8J TK4- distribution (update 8) which you can get from here.  Notice that we don't actually use the MVS3.8J distrubution at all, we only use the Hercules binaries that come with TK4-. You find them under ../hercules/linux/64/bin 2. The MVS 3.8J with JES3 distribution from Kevin's website. Notice that I have a MVS3.8A and a MVS3.8B directory. A is for the global MVS image and B is for the local MVS image. You need both TK4A:   http://www.j76.org/misc/tk4-_ update_07.jes3_2016-09-15.zip TK4B:   http://www.j76.org/misc /tk4-_update_07.jes3b_2016-10- 04.zip Or you can also get them from here :  3. any 3270 t
Read more

IBM MVT 21.8F Distributions for Hercules

What's MVT? MVT is a beautiful operating system. Extremely reliable and a great way to learn and understand the modern day successor (or grand-grand-grandchild), z/OS.  When IBM announced the System/360 mainframe line in April 1964, the plan was to provide just one operating system for batch-oriented use, known simply as the System/360 Operating System (less formally as OS/360, or OS). OS was big, complex and ambitious for its day, and the resulting system was late, buggy and resource-intensive. Installations that couldn't wait, or couldn't afford the hardware required to run OS, opted for one of the smaller, simpler systems that IBM created as alternatives: BOS/360, TOS/360, DOS/360. Eventually, with most of the bugs shaken out OS/360 became IBM's flagship System/360 operating system. By the time of the final OS/360 release in 1974, system programmers building an OS system had the choice of two control programs: MFT, Multiprogramming with a Fixed number of
Read more

Old, old software

Lately, a bunch of 3420 tape reels were found. After converting them into electronic format, we unearthed several software products that were thought to be lost forever: 1. EDGAR 2. 5740-CB1 RELEASE 2.4 IBM OS/VS COBOL JULY 1, 1982 for MVS This is the follow-on release to the MVT Cobol that we know from MVS 3.8 TK4-. Both are ANSI Cobol compilers, but this one has a several novelties compared to the Release 1.3 of TK4-: an optmizer, VSAM support, a LIST parameter to create an assembler listing, and better RENT checking. 3. CP/67 CMS Source code See more here:
Read more