开云体育

I don’t think that the original poster is running MVS 3.8 but OS/390 or newer since has a TCPIP profile dataset. -trp What version of MVS or OS/390 or z/OS are you running? Also are you using the

Turnkey includes the MVS 3.7 starter system on a stand alone volume for this purpose. And the renames may work under the Turnkey system and only need the IPL to pick up the new dataset.

Can you just copy CENTER.PARMLIB into your own (large enough) SYSPRG1.PARMLIB, edit TCPPROF to your taste, and then use PARMLIB concatenation in SYS1.IPLPARM to have the system use that dataset

Thanks for the reply, Mike. Well, if it's the only way, that's what I shall do. I'll probably need to generate another system, though. Att., -trp

That is for the tk4- ftp. It’s not used in esa or z/arch. It enables the FTP in tk4- As I recall it’s not 64 bit safe. Laddie Sent from whatever device I am using.

if you want to learn to use VSAM with an API, then start with Jay's interface. You will then have a MUCH better understanding when you go to KICKS. joe

The last time I used ISAM was 1981 when I was in college and the system was?a 360/67 running MVT 22.8F. ISAM fell out of favor as MVS matured in the late 70’s. ISAM was functionally stabilized at

Hello Joe, Am 26.12.2020 um 17:32 schrieb Joe Monk <joemonk64@...>: May I ask you to elaborate in more detail? Allow me to explain a few more details. I want to use TK4-, so the only COBOL

IPL with the starter system. Create a new name, copy the members over. Rename old dataset. Rename new dataset. IPL with normal system.

Standard practice for production batch files in all the shops I have ever worked was to initialize files (ISAM or VSAM included) with a header record with a binary-zeroes key value and a date and

High values is still required for various system datasets. <rupertreynolds@...> wrote:

Thank you, both of you. It works well either way. What's more intriguing is that I didn't find it easily in the manuals and Redbooks. Anyway, there's, now, a second issue. The dataset is accessible,

Standard practice when I was involved was to use REPRO to copy dummy data into any new VSAM dataset, to initialise it. I can't remember whether it was one record (with a low key, to be ignored or

Good point, but I prefer to leavw the prefix, and simply use apostrophes around dataset names that don't start with it. sub d(myjob) is easier to type than sub roopy.d.cntl(myjob) Same with ex

TCPIP is not active by default in Hercules.? The following may give you some clues about how to activate it.? The availability and flavor of the instruction is controlled by three elements: 1.? The

TSO PROFILE NOPREFIX. Then try to access your dataset. Joe

Yeah ... DONT use ISAM. You will regret it if you do so. USE VSAM KSDS instead. Easier and less complicated. If you need some pointers let me know. Joe

Hi, all I have a rather dumb question, I recognize. But I've been struggling with it for the past day. There's a data set (CENTER.PARMLIB) in which TCPPROF member is contained. TSO MVSCUST opens this

Hello, "The records that comprise a newly created data set must be presented for writing in ascending order by key." Source:

When Hercules writes the data from memory cache to disk, it compresses the data and writes at a new location. The old location is marked as available and the files is eventually compressed to remove