开云体育

Holy COW! I added a new one with 4 chars and that did the trick. For the sake of completeness I went to the old one, change something then UPDATE and the message said: THIS IS A NON-ICCF USER, NO

That is probably the source of the problem. On my system, for access to VSE/ICCF, you need a userid with no more than 4 characters. Check the attached documentation. Cheers, Rene FERLAND, Montreal

As I recall there’s a place in the user profile where you grant ICCF access. I am not currently at my computer but I’ll see if I can get you more details on how to do this

Hi Rene, Is SERGIOS (7 chars). Options I cannot use: "Program Development Library" "Create Application Jobstream" "File Management" "Command Mode" trying to use them the message (verbatim) is: "THE

What is the name of your new user ? Cheers, Rene FERLAND, Montreal

I created a new user based in sysa but in any menu option I get "YOU ARE NOT AUTHORIZED TO USE ICCF". What I'm missing?

Great! That's good news, thanks for sharing. Cheers, René FERLAND, Montréal

I did fix that. Now my vm/esa accepts 3350 disks. This can be achieved by modifying the hcprio assemble file something like this: RDEVICE DEVNO=(140,16),DEVTYPE=3350 RDEVICE

DOS/VS R34 is available on 3350 disks and I think VM/ESA does not support 3350 anymore. Cheers, René FERLAND, Montréal

When I try to boot dos/vs 34 under VM/ESA it dies with disabled psw. The same config works fine under hercules directly. I defined VM as 370 already.

I don't know how it works, but I found what I believe is the source of the syntax: compvse.m4 in my fork of gcc 3.2.3 * assemble %s * // DLBL IJSYSLN,,0,SD // EXTENT SYSLNK,,,,14000,1000

// DLBL IJSYSLN,,0,SD // EXTENT SYSLNK,,,,12000,2000 SPACE-LINK ASSGN SYSLNK,SYS000 // OPTION CATAL // DLBL IJSYSIN,'PDPPUNCH.DAT' ASSGN SYSIPT,SYS000 INCLUDE CLOSE SYSIPT,READER // EXEC LNKEDT ASSGN

I have now proved the concept sufficiently. If you write your programs a certain way, you can stand up a clone anywhere (e.g. you can run VSE programs on z/OS). But I have my own environment

This was close to day one on DOS/VS not MVS: CICS *1*.1. I can not speak to the situation on MVS.? My MVS experience was a couple decades later and my CICS work was as a systems programmer (as we

Interesting :) I always thought ASKTIME and EIBDATE and EIBTIME were around since day 1. Joe <h.grovsteen@...> wrote:

Yes, you can just inspect low memory to locate the COMRG. In the early days of COBOL programming in CICS/VS 1.1 on DOS/VS, there was a mechanism that allowed me to define a COBOL area that had a

Thanks for that explanation. Ok - I had the wrong concept there - thanks. BFN. Paul.

Paul Edwards wrote: I am going to presume you know what a partition is in DOS/VS. Each partition has its own Communications Region. Address 20 is always set to the address of the given partition's

COMRG causes the address of the partition communications region to be placed in R1. [image: image.png] "Or is that not how the PSA works when there are multiple processors or something like

What's the rationale here? We're trying to get the address of a common region. COMRG L 1,20 SVC 33 LR R5,R1 USING COMREG,R5 The first thing it does is load a value from absolute address