开云体育

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:

Joe: I did already try this on an earlier iteration, including reformatting the spool. On my TK5 Update 3 system, it is in SYS1.JES2PARM(JES2PARM). It did not have the desired effect.

And dont forget to format the SPOOL, a necessary step to change the system ID. When IPL'ing, at the JES2 request screen: R 02,Format,noreq Joe [email protected]> wrote:

So, in JES2 parms in SYS1.PARMLIB, you may see this parameter: [image: image.png] Joe [email protected]> wrote:

That is in a different file AND it is not easy to change. I did look at it some years back and decided it was too much like hard work and not important. Hopefully some one will give you the name a

I've changed my SID in SYS1.PARMLIB(SMFPRM00).? The new SID displays as expected on the main ISPF menu screen.? However, the TSO logon message that displays prior to the first menu load still

thank you guys for the big yob you are doing !