Re: VTOCs vs. catalogs

2024-05-23 Thread Tom Brennan
Thanks! You answered my questions. I always figured there was a time before catalogs, when I assume you had to code VOL=SER= on everything, but that was before my time. And I was trying to remember the CVOL method. I started with ICFCAT's but come to think of it, there may have been one or

Re: VTOCs vs. catalogs

2024-05-23 Thread Attila Fogarasi
VSAM catalog was released in 1974 in OS/VS2 R2, prior to that the catalog was CVOL (dsname SYSCTLG with BLKSIZE=256 and KEYLEN=8). The SYSRES volume was the primary SYSCTLG but could be linked to CVOL on other volumes. The "new" VSAM catalog in 1974 was a big improvement. On Fri, May 24, 2024

Re: VTOCs vs. catalogs

2024-05-23 Thread Joel C. Ewing
VTOCs did come first.   The  original DOS/360 Operating System did not have catalogs.   VTOCs contain not only information about physical location and organization of datasets on the volume but also (for OS/360 and its MVS and z/OS descendants) contains a list of all the free extents on the

Re: VTOCs vs. catalogs

2024-05-23 Thread Gibney, Dave
All speculation on my part. One system with no DASD, you need neither. On a system with only one, of just a few DASD volumes, a VTOC is required to say where on the volume a dataset is and the basic attributes of PS and PDS datasets. Once you get to several always mounted DASSD volumes, it

Re: VTOCs vs. catalogs

2024-05-23 Thread Mike Schwab
For the most part the catalog lets you locate your dataset no matter which volume you put it on. For non-vsam, that is about all that is stored, dataset characteristics are in the VTOC. And with non-SMS volumes you can have uncataloged datasets on DASD or tape. VSAM came from the Future Systems

Re: Getting 4088/00000063 in CICS

2024-05-23 Thread Attila Fogarasi
Stack segment owning the next-available-byte (NAB) could not be found or a DSA backchain pointer did not contain a valid 31-bit addressable address. Possible reason is storage overlay or wrong addressing mode. DSA backchain pointers must contain valid addresses that can be accessed as is while in

VTOCs vs. catalogs

2024-05-23 Thread Phil Smith III
I'm curious whether any of you old-timers can explain why we have both VTOCs and catalogs. I'm guessing it comes down to (a) VTOCs came first and catalogs were added to solve some problem (what?) and/or (b) catalogs were added to save some I/O and/or memory, back when a bit of those mattered.

Re: IBM Sterling Connect:Direct for z/OS Version 6, Release 2

2024-05-23 Thread Sasso, Len
The latest from IBM: "Hello Len, The DGASACMP program will not accept QPL_FLAG_GZIP_MODE.  In our documentation ( https://www.ibm.com/docs/en/connect-direct/6.2.0?topic=dgasacmp-parameters ) we specify what parameters that can be passed to the DGASACMP program. I did a Google search on  

Re: IBM Sterling Connect:Direct for z/OS Version 6, Release 2

2024-05-23 Thread Steve Thompson
Len: Even if they are not Mainframe based, they should have the "utility" for their system if they are running Connect:Direct for that system. Otherwise, they are going to fail the hand-shake for the XFER protocols used by C:D, unless the new owners have made other changes to have C:D use

Re: IBM Sterling Connect:Direct for z/OS Version 6, Release 2

2024-05-23 Thread Sasso, Len
Tony: Most, if not all, of our customers are not mainframe based. Thank You and Please Be Safe. Please Note: I would appreciate it if you would please include my teammates ("rdc_applications_...@gdit.com") in future emails to keep them informed. Len Sasso Systems Administrator Senior CSRA,

Re: IBM Sterling Connect:Direct for z/OS Version 6, Release 2

2024-05-23 Thread Cieri, Anthony
Hi Len , Check with IBM on your open Case, but I suspect that GZIP is NOT compatibleYour remote client should already have a copy of DGASACMP.. Why not just use that..??? Thanks Tony -Original Message- From: IBM Mainframe Discussion List

Re: IBM Sterling Connect:Direct for z/OS Version 6, Release 2

2024-05-23 Thread Sasso, Len
Good afternoon, Tony! I found the manual and opened Case TS016307677 - Connect:Direct - DGASACMP Program Parameters: Can this program accept a parameter (QPL_FLAG_GZIP_MODE flag) to add GZIP header and trailer information to the output stream (when performing compression)? If this is

Re: IBM Sterling Connect:Direct for z/OS Version 6, Release 2

2024-05-23 Thread Cieri, Anthony
Len, Check out the following manual; IBM Connect:Direct for z/OSVersion 6.1. On page 653 is an example of the Batch Compression utility (DGASACMP). You can run this and then transfer the file Good Luck Tony -Original

Re: REXX SDSF

2024-05-23 Thread Roberto Halais
Thank you Paul for your suggestion. I used the following: Usscmd = ‘nestat -t -M LONG’ call bpxwunix usscmd,,out.,stde. I got the output that I wanted and not written to syslog. On Tue, May 21, 2024 at 4:03 PM Paul Feller < 05aa34d46684-dmarc-requ...@listserv.ua.edu> wrote: > There is

Re: IBM Sterling Connect:Direct for z/OS Version 6, Release 2

2024-05-23 Thread Sasso, Len
Good morning, Steve! Could you please provide an example of running compression in a run task and then sending the resulting file to the target system? Or point me to a manual that provides an example? Thank You and Please Be Safe. Len Sasso Systems Administrator Senior CSRA, A General

Re: Getting 4088/00000063 in CICS

2024-05-23 Thread Binyamin Dissen
PTF was already applied. Module at UI83147. Looked at save area pointed to by TCAREGPT and it looks fine. What precisely is LE complaining about? On Thu, 23 May 2024 06:56:34 +1000 Attila Fogarasi <05b6fee9abb7-dmarc-requ...@listserv.ua.edu> wrote: :>Sounds like you don't have PH24895

Re: How to convert these IMS unload files from EBCDIC to UTF-8 encoding

2024-05-23 Thread ITschak Mugzach
All major relational databases support variable length data load (incl. DB2) . This is not a problem at all. ITschak Mugzach *|** IronSphere Platform* *|* *Information Security Continuous Monitoring for z/OS, x/Linux & IBM I **| z/VM coming soon * On Wed, May 22, 2024 at 11:41 PM Tom Ross