开云体育

On Tue, 30 Apr 2024 06:39:40 +0200, Mike Gro?mann <mike.grossmann.de@...> wrote: Hi Mike, I have understood as much from the messages regarding the problem/annoyance. ;) I have

Nothing stupid; tar -cjvf is the command used; and Hercules was not active when doing the tar command.? It creates the tar ball; but the tar ball is useless on cckd64 files. regards; Rahim???

Hello Fernando, The RAKF messages regarding DIAG8CMD and SVC244 are triggered by BREXX. BREXX is checking for these RAKF profiles. Unfortunately RAKF has the default behavior to log such profile

Jo?o Reginato wrote: [...] And dasd device type whose architected capacity is 4GB or more should use either the CKD or CCKD64 formats. CKD if you don't mind having very large files consuming gobs of

Rahim Azizarab wrote: Sounds like a bug in bzip2 and/or tar to me. In any case, you can be certain it has absolutely nothing to do with Hercules. AFAIK tar and/or bzip2 doesn't give a rat's ass WHAT

This might be a problem with bzip. Tar and bzip are theoretically compressing and decompressing the same bytestream… You might try using variations with cpio and other compression tools…

On Sat, 27 Apr 2024 05:15:47 -0700, "Rob Prins" <prin0096@...> wrote: Thank you Rob at al. Complete clueless newbie here. Just followed the update from 2 to 3 in the webpage.

Ok, Another related questions: Is there any format recommendation for 3390-3 or 9 or 27? Is there performance gain copying to another format? De: [email protected] <[email protected]>

CCKD64 for some reason does not like to get tared and bzip2ed subsequently I can't make a reliable backup tar ball of the system when using CCKD64.? The problem did not exist with the plain cckd dasd

The entry is in SMFPRMxx of parmlib.

Fish wrote: [...] See also: * https://sdl-hercules-390.github.io/html/cckddasd.html#filestructure -- "Fish" (David B. Trout) Software Development Laboratories http://www.softdevlabs.com mail:

Joe Monk wrote: ALMOST correct. :) CKD = uncompressed, period. There are no internal file format file pointers involved with accessing plain CKD files. Track data on plain CKD files are directly

CKD = uncompressed native with 32-bit pointers CCKD = compressed native with 32-bit pointers CCKD64 = compressed with 64-bit pointers Otherwise, they are the same Joe [email protected]> wrote:

Hi everybody What are the real differences between these file formats? CKD, CCKD and CCKD64 TIA Jo?o

Actually, on TK5 Update 3, by a REXX script, SYS2.EXEC(WELCOME), which reads a SMF record to get the SID. Cheers, Rene FERLAND, Montreal

On Sun, 28 Apr 2024 12:54:37 -0400, "Daniel L. Srebnick via groups.io" <dan@...> wrote: Isn't that "Welcome" message issued by a TSO starting CLIST? HTH > Hi again Joe: >

It appears that there is an error in SYS.EXEC(WELCOME). SYS2.EXEC(WELCOME) says: "tit1="Welcome to the TSO system on " || peeks(smca()+24,4)" It is using a BREXX function to get the system

Hello Daniel, On TK5, the welcome message is produced by a REXX script located in SYS2.EXEC(WELCOME). That? script uses the SMF SID to write its message. So, I think you need to update

Hi again Joe: Referring back to my original post, the SYSTEM ID as shown on the ISPF main screen is correct without setting &SID in JES2PARM. Where it is not correct is on the welcome message as

[image: image.png] Changing SID parameter in SMF and JES: [image: image.png] [image: image.png] After RE-IPL and SPOOL Format... [image: image.png] Joe [email protected]> wrote: