开云体育

Opss It's the same group FISH, they'll probably complain to me again. Enviado do Email<https://go.microsoft.com/fwlink/?LinkId=550986> para Windows 10 De: Blade

Re send. Enviado do Email<https://go.microsoft.com/fwlink/?LinkId=550986> para Windows 10 De: Fish Fish<mailto:david.b.trout@...> Enviado:sábado, 1 de agosto de 2020 18:23 Para:

Mattis ... Last attempt. [image: image.png] Where are all of the patches that were on the system prior to the IOGEN? When did they get applied? Joe

Joe, Please read what I have written. First, the ABEND is there BEFORE the IOGEN has taken place and is a result of the step (6) where all the user mods are removed. I can IPL that snapshot and I get

We still do it that way in a lot of cases ... -- Drew Derbyshire "I want to be alone." -- "Grand Hotel"

Mattis, Think about it. If you build a brand new nucleus, and it is abneding on attempting to IPL, what does that mean? It means the nucleus is missing mods that make it work. Joe

Hello Jay! I know that your instructions are for your build primarily. And of course using them on some other build would maybe not work at all. I fully understand that. I learnt a lot from doing you

Nope. That happens already after doing step 6 above. So it has nothing to do with the IOGEN. /Mattis

No, but prior to do the IOGEN, after doing the removal of all the customizations, i.e. step 6, in the top message? I was able to login. Essentially, the system is exactly in the same state, except

BTW, Welcome to the frustrating world of SYSGEN/IOGEN! This is how we used to do it, long before PCs ever existed. Trial/Error. Joe [email protected]> wrote:

A good. example of that is this message in the log: 4000 13.36.31 STC 72 IEF450I CMD1 CMD1 - ABEND S000 U0077 So the system is not properly configured post IOGEN. Joe [email protected]> wrote:

Mattis, After you ran the IOGEN, did you reapply all of the customization that had been done post SYSGEN? If not, the system will not start correctly (i.e. no TSO, VTAM not correct, etc.) When you do

These are usually warnings that may be ignored, but you can track down the output from the Link Editor in the SYSOUTs to verify. Most of the generated jobs will include a message similar to: "EXPECT

Yes. I by mistake removed the initiator for class C. With in place the jobs, IOG11 to IOG15 was able to pass through quite OK: Except for these that had 0004: Not sure if this is good or bad? My

Hi Peppe, Below you will find an example for a HEXCONV. This piece of code is used in the RPF browser for load modules. HEXCONV? DS??? 0H ST??? R14,SAVE14HX??????????? Save register

Thanks Rob, your advices are appreciated. Currently, as an example, I'm looking to a PL/I (for the modern Z/OS PL/I compiler) assembler routine DWNSHEX (got it from CBT, I don't remember the name of

Hi Peppe, An EX instruction is OR'ing the low order 8 bits of the R1 (mentioned in the EX instruction) over bits 8-15 of the instruction that is OR'ed. So be careful to EX to a SS-2 type instruction.

Yep, I think I'm converging ;-) TR/MVC instructions have an LL field which may handle up to 256 bytes, while UNPK use the LL field for both source and target, up to 7 digits. Which lead to a loop for

Ouch, I missed this, thanks Rob! So it is actually easier, maximum 7 bytes, i.e. 14 hex digits. In any case probably the "EX" instruction is the easier way to go? Shouldn't coding unrolled 7 routines

Yes, EX is used to put varying lengths into instructions. And if you are doing 4 or 8 groups of 8 nibbles and a blank into a print line of 80 or 132, do the unpacks then translate the bytes then move