Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- H390-DOSVS
- Messages
Search
|
Re: How to run DOS/VS 34 under VM/ESA
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 DEVNO=(150,8),DEVTYPE=3330,MODEL=1 ? ? ? ? ?RDEVICE DEVNO=(160,8),DEVTYPE=3340 ? ? ? ? ?RDEVICE DEVNO=(170,8),DEVTYPE=3375 ? ? ? ? ?RDEVICE DEVNO=(240,16),DEVTYPE=3350 ? ? ? ? ?RDEVICE DEVNO=(270,8),DEVTYPE=3375 ? ? ? ? ?RDEVICE DEVNO=(340,16),DEVTYPE=3350 ? ? ? ? ?RDEVICE DEVNO=(360,8),DEVTYPE=3350 ? ? ? ? ?RDEVICE DEVNO=(6A0,16),DEVTYPE=3350 ? ? ? ? ?RDEVICE DEVNO=(6B0,16),DEVTYPE=3350 ? ? ? ? ?RDEVICE DEVNO=(6C0,16),DEVTYPE=3350 ?
This then avoids loop when vm/esa tries to sense disks.? |
|
Re: VSE mini-clone
On Sat, Sep 14, 2024 at 08:29 PM, Joe Monk wrote:
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 SPACE-PHASE ASSGN SYSLNK,SYS000 // OPTION LINK // OPTION CATAL,LIST PHASE %s,S+80 // DLBL IJSYSIN,'%s.ASM' ASSGN SYSIPT,SYS000 // EXEC ASSEMBLY CLOSE SYSIPT,READER * * * * * link %s * INCLUDE VSESTART INCLUDE STDIO INCLUDE STRING INCLUDE STDLIB INCLUDE CTYPE INCLUDE ERRNO INCLUDE LOCALE INCLUDE MATH INCLUDE SIGNAL INCLUDE SETJMP INCLUDE ASSERT INCLUDE TIME INCLUDE START INCLUDE VSESUPA ENTRY @@MAIN // EXEC LNKEDT ASSGN SYSLNK,UA * BFN. Paul. |
|
Re: VSE mini-clone
// 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 SYSLNK,UA What?is the purpose of this? ASSGN SYSLNK,SYS000 When you do this... ASSGN SYSIPT,SYS000? you override your SYSLNK?assignment. Joe On Sat, Sep 14, 2024 at 6:16?AM Paul Edwards via <mutazilah=[email protected]> wrote: I have now proved the concept sufficiently. |
|
VSE mini-clone
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 - z/PDOS-generic, so that's what I am using. Here is what a VSE program looks like when running: (I renamed the executable from pdptest.exe to vsetest.exe) 18:48:59 /(0009) vsetest.exe 18:48:59 got request to open vsetest.exe 18:48:59 in LoadVSE 18:48:59 about to call app at address 04ECE818 18:48:59 got service call 0 18:48:59 len is 8 18:48:59 msg is MADE IT! 18:48:59 got service call 7 18:48:59 return from app is hex 3 18:48:59 18:48:59 enter a command That same program running under DOS/VS: 19:00:12 BG 19:00:12 * 19:00:12 BG 19:00:12 * 19:00:12 BG 19:00:12 * Now run the app 19:00:12 BG 19:00:12 * 19:00:12 BG 19:00:12 MADE IT! 19:00:12 BG 19:00:12 * 19:00:12 BG Using this JCL: * First we get the main phase off tape, and into 80-byte blocks * using objmaint * // UPSI 1 // ASSGN SYS004,TAPE // DLBL UOUT,'PDPPUNCH.DAT',0,SD // EXTENT SYS005,,,,10000,2000 SPACE-PHASE // ASSGN SYS005,SYS000 // EXEC OBJMAINT,SIZE=AUTO ./COPY /* // UPSI 0 // ASSGN SYS005,SYSLST // ASSGN SYS004,UA * * * * * * * * Then we put the phase into the CIL, using LNKEDT * // 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 SYSLNK,UA * * * * * * * Now run the app * // EXEC PDPTEST,SIZE=AUTO,PARM='PaulEdwards two Three' And here is the program itself: 000000 40D7C8C1 E2C540D7 C4D7E3C5 E2E36BE2 PHASE PDPTEST,S 000010 4EE77DF0 F0F0F0F5 F07D4040 40404040 +X'000050' 000020 40404040 40404040 40404040 40404040 000030 40404040 40404040 40404040 40404040 000040 40404040 40404040 40404040 40404040 000050 02C5E2C4 40404040 40400010 40400001 .ESD .. .. 000060 D7C4D7E3 C5E2E340 007000C8 40001330 PDPTEST ...H ... 000070 40404040 40404040 40404040 40404040 000080 40404040 40404040 40404040 40404040 000090 40404040 40404040 40404040 F0F0F0F1 0001 0000A0 02E3E7E3 407000C8 40400038 40400001 .TXT ..H .. .. 0000B0 47F0F010 D7C7C3E7 00000004 00000000 .00.PGCX........ 0000C0 5810F070 58101000 12114780 F02C90EC ..0.........0... 0000D0 D00C41D0 D05018CF 47F0C040 18CF187E }..}}&...0{ ...= 0000E0 5830C074 5840C078 40404040 F0F0F0F2 ..{.. {. 0002 0000F0 02E3E7E3 40700100 40400038 40400001 .TXT ... .. .. 000100 5850C07C 41D0C088 4190D050 5090D04C .&{@.}{h..}&&.}< 000110 58F0C080 05EF58F0 C07418E7 5810C070 .0{....0{..X..{. 000120 58101000 12114780 C06E5BD0 C08458E0 ........{>$}{d.\ 000130 D00C980C D01407FE 40404040 F0F0F0F3 }.q.}... 0003 000140 02E3E7E3 40700138 40400038 40400001 .TXT ... .. .. 000150 007000D4 00000003 00000004 00000005 ...M............ 000160 0070122C 00000050 00000000 00000000 .......&........ ... 001AB0 05EF1F22 18F258D0 D00458ED 000C980C .....2.}}.....q. 001AC0 D01407FE 00000000 D4C1C4C5 40C9E35A }.......MADE IT! 001AD0 00000150 00701340 40404040 F0F0F8F5 ...&... 0085 001AE0 02E3E7E3 40701328 40400038 40400001 .TXT ... .. .. 001AF0 09000000 00000000 00701344 FFFF8000 ................ 001B00 00000007 00000008 00701250 47F0F00A ...........&.00. 001B10 055F5F73 766390EC D00C58F0 D04C50D0 .^^.....}..0}<&} 001B20 F00450F0 D00818DF 40404040 F0F0F8F6 0.&0}... 0086 001B30 02E3E7E3 40701360 40400038 40400001 .TXT ..- .. .. 001B40 18B105C0 5AF0C080 50F0D04C 58A0C084 ...{!0{.&0}<..{d 001B50 5820C088 58202000 12224770 C040D203 ..{h........{ K. 001B60 D058B000 D203D05C B004D203 D060B008 }...K.}*..K.}-.. 001B70 4110D058 58F0C08C 40404040 F0F0F8F7 ..}..0{. 0087 001B80 02E3E7E3 40701398 40400038 40400001 .TXT ..q .. .. 001B90 05EF182F 5020D068 47F0C06E 5820C088 ....&.}..0{>..{h 001BA0 58202000 D203D058 B000D203 D05CB004 ....K.}...K.}*.. 001BB0 D203D060 B0085820 220C4110 D05841F0 K.}-........}..0 001BC0 200005EF 182F5020 40404040 F0F0F8F8 ......&. 0088 001BD0 02E3E7E3 407013D0 40400028 40400001 .TXT ..} .. .. 001BE0 D06858F0 D06858D0 D00458ED 000C980C }..0}..}}.....q. 001BF0 D01407FE 00000070 007013F4 007000D4 }..........4...M 001C00 007010F0 00701364 40404040 40404040 ...0.... 001C10 40404040 40404040 40404040 F0F0F8F9 0089 001C20 02D9D3C4 40404040 40400038 40404040 .RLD .. 001C30 00010001 0D700138 0D700148 0D7011C8 ...............H 001C40 0D7011D4 0D7011D8 0D701224 0D701228 ...M...Q........ 001C50 0D701324 0D701330 0D701340 0D7013E8 ........... ...Y 001C60 0D7013EC 0C7013F0 40404040 F0F0F9F0 .......0 0090 001C70 02D9D3C4 40404040 40400004 40404040 .RLD .. 001C80 00010001 0D7013F4 40404040 40404040 .......4 001C90 40404040 40404040 40404040 40404040 001CA0 40404040 40404040 40404040 40404040 001CB0 40404040 40404040 40404040 F0F0F9F1 0091 001CC0 02C5D5C4 407000C8 40404040 40400001 .END ..H .. 001CD0 40404040 40404040 40404040 40404040 001CE0 40404040 40404040 40404040 40404040 001CF0 40404040 40404040 40404040 40404040 001D00 40404040 40404040 40404040 F0F0F9F2 0092 001D10 615C4040 40404040 40404040 40404040 /* 001D20 40404040 40404040 40404040 40404040 001D30 40404040 40404040 40404040 40404040 001D40 40404040 40404040 40404040 40404040 001D50 40404040 40404040 40404040 40404040 (and attached in full) There is still one technical problem I'm waiting on (malformed RLD), but it doesn't stop it from running. The technique I am using involves getting z/PDOS-generic to zap the executable on loading. The start assembler needs to look like this: __crt0: B skiphdr # .byte "PGCX" # PDOS-generic (or compatible) extension # Needs to be in EBCDIC .byte 0xd7, 0xc7, 0xc3, 0xe7 # .long 4 # length of header data .DC F'4' .globl __pgparm __pgparm: .long 0 # This will be zapped by z/PDOS-generic if running under it skiphdr: L R1,=V(__pgparm) L R1,0(,R1) LTR R1,R1 BZ notpdos STM r14,r12,12(r13) LA r13,80(,r13) LR r12,r15 .drop r15 .using __crt0, r12 B BYPASS1 notpdos: LR r12,r15 pgparm gets zapped by z/pdos-generic like this: #ifdef NEED_VSE os.Xservice = service_call; if (memcmp(entry_point + 4, "PGCX", 4) == 0) { *(void **)(entry_point + 12) = &os; } #endif Service calls are handled like this: #ifdef NEED_VSE #include <mfsup.h> static int service_call(int svcnum, void *a, void *b) { printf("got service call %d\n", svcnum); if (svcnum == 0) { REGS *regs; CCB *ccb; CCW *ccw; char *msg; regs = a; ccb = (CCB *)regs->r[1]; ccw = ccb->actual.ccw_address; msg = (char *)(ccw->actual.addr & 0xffffff); printf("len is %d\n", ccw->actual.len); printf("msg is %.*s\n", ccw->actual.len, msg); } return (0); } #endif This C code in the application avoids doing a real SVC: int __svc(int svcnum, void *regsin, void *regsout) { if (__pgparm == 0) { return (__svcreal(svcnum, regsin, regsout)); } else { return (__pgparm->Xservice(svcnum, regsin, regsout)); } } On real DOS/VSE (or z/VSE) it will do a real SVC. It is my intention to stand up CMS and MVS mini-clones the same way. To the point where they can at least run arbitrary C programs. I'm not sure what to do then though. I'm not sure if there is a market for a mini clone of a mainframe OS. I'm not necessarily trying to be in a market though. But maybe it would be good if someone else was so that IBM had some competition. I was thinking of maybe setting up a rival to India in Vietnam. BFN. Paul. |
|
Re: COMRG
开云体育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 referred to the job in those days).? Not application
programmer, as I was in the 70's when my work experience was
DOS/VS. Harold Grovesteen On 9/11/24 17:37, Joe Monk wrote:
|
|
Re: COMRG
Interesting :) I always thought ASKTIME and EIBDATE and EIBTIME were around since day 1. Joe On Wed, Sep 11, 2024 at 5:24?PM Harold Grovesteen via <h.grovsteen=[email protected]> wrote: Yes, you can just inspect low memory to locate the COMRG. |
|
Re: COMRG
Yes, you can just inspect low memory to locate the COMRG.
toggle quoted message
Show quoted text
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 pointer set to 20, and lo and behold you could access the date from the COMRG without issuing an SVC which was not a good idea in a CICS application.? The date was what I needed.? But anything was there for the reading. By avoiding SVC 33, CICS, the partition, did not lose control. How COBOL implemented CICS table accesses via a COBOL defined base-address register field was the basis for the pointer. Just FYI from the early days.? CICS/VS with COBOL applications provided no mechanism for accessing the date (that I recall).? IBM support found my solution "interesting". Harold Grovesteen On 9/11/24 16:36, Paul Edwards wrote:
On Wed, Sep 11, 2024 at 11:34 PM, Fish Fish wrote:Each partition has its own Communications Region. Address 20 is always set toThanks for that explanation. |
|
Re: COMRG
On Wed, Sep 11, 2024 at 11:34 PM, Fish Fish wrote:
Each partition has its own Communications Region. Address 20 is always set toThanks for that explanation. Ok - I had the wrong concept there - thanks.Or alternatively - use the abstraction - SVC 33 can go andThat is not the purpose of SVC 33. BFN. Paul. |
|
Re: COMRG
Paul Edwards wrote:
What's the rationale here?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 Communications Region control block by the dispatcher. It is a part of task dispatching. So while that particular partition is running, address 20 always points to its COMRG. Or alternatively - use the abstraction - SVC 33 can go andThat is not the purpose of SVC 33. Or is that not how the PSA works when there are multiple processorsI don't believe DOS/VS supported multiple processors. It only supported multiple partitions. It is just a very simple multitasking operating system. SVC 33 is, as far as the user is concerned (or should I say, as far as USER tasks are concerned), a dummy SVC that essentially does nothing. It simply goes directly to the dispatcher to return back to the caller. If a SYSTEM task issues SVC 33 however, it causes the dispatcher to dispatch a higher priority system task instead, if there is one. (User tasks and system tasks are dispatched differently. User task priorities can change (via the operator PRTY command), whereas system tasks have hard coded fixed priorities.) To better understand the purpose of SVC 33 (i.e. how it works), all one need do is examine the DOS/VS Supervisor code (listing) for it. (Everyone should have a copy of an assembled supervisor listing on their system for reference IMO. You can learn a lot by studying it): 01098 1331+SVC33 EQU * . @DM01378 20100028 1332+* SVC33 IS A DUMMY SVC WHEN ISSUED BY A USER TASK @DM01378 20100828 1333+* SVC33 ISSUED BY A SYSTEM TASK DEACTIVATES TASK @DM01378 20101628 1334+* WHICH IS ACTIVE VIA SELECT BYTE. THIS ALLOWES @DM01378 20102428 1335+* DISPATCHER TO GIVE CONTROL TO ANY HIGHER @DM01378 20103228 1336+* PRIORITY SYSTEM TASK @DM01378 20104028 001098 9500 073D 0073D 1337+ CLI SELECT,ZERO . SVC33 ISSUED BY SYST.TASK @DM01378 20110028 00109C 0786 1338+ BCR E,R6 . NO,GOTO TASK SELECTION @DM01378 20110828 00109E 1876 1339+ LR R7,R6 . SETUP EXIT ADDRESS @DM01378 20111628 0010A0 4140 0083 00083 1340+READYSYS LA R4,READY . SETUP DESELECT ROUT. @DM01378 20112428 1341+* FOLLOWING ROUTINE CLEARS SELECT BITE AND SETS @DM01378 20112528 1342+* SYSTEM TASKS PIBFLAG TO A VALUE CONTAINED IN R4 @DM01378 20112628 0010A4 5850 0794 00794 1343+DESELECT L R5,ASYSBLKX . ADDRESS OF SYS.TASK BLOCK @DM01378 20113228 00000 1344+ USING SYSBLKS,R5 @DM01378 20114028 0010A8 4880 5000 00000 1345+ LH R8,SYSPIBFL . ADDRESS OF SYS.TASK PIBFLAG @DM01378 20114828 00000 1346+ USING SPIBADR,R8 @DM01378 20115628 0010AC 4240 8000 00000 1347+ STC R4,SPIBFLG . SET TASK TO READY OR BOUND @DM01378 20116428 0010B0 9200 073D 0073D 1348+ MVI SELECT,ZERO . DEACTIVATE TASK IN SELECT @DM01378 20117228 0010B4 07F7 1349+ BR R7 . RETURN TO CALLER OR TO EXIT @DM01378 20118028 -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@... |
|
Re: COMRG
COMRG causes the address of the partition communications region to be placed in R1. "Or is that not how the PSA works when there are multiple processors or something like that?"There is no PSA in DOS/VS. Joe On Tue, Sep 10, 2024 at 11:41?PM Paul Edwards via <mutazilah=[email protected]> wrote: What's the rationale here? |
|
COMRG
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 20. And then it does an SVC 33 - which provides a level of abstraction I think. But you've just defeated that abstraction by accessing an absolute address. If you're willing to start at an absolute address, you may as well have your control blocks chained off that. Perhaps this isn't considered to be a control block - it is specific to this program and there could be a chain of such programs. Or alternatively - use the abstraction - SVC 33 can go and inspect low memory itself? Or is that not how the PSA works when there are multiple processors or something like that? Thanks. Paul. |
|
Re: pdld
I now have the equivalent of WTO working, with the CCB/CCW/EXCP in C.
You can see that here: 09:01:22 BG 09:01:22 * 09:01:22 BG 09:01:22 * Now run the app 09:01:22 BG 09:01:22 * 09:01:22 BG 09:01:22 MADE IT! 09:01:22 BG 09:01:22 * 09:01:22 BG So next I will work on adding those services to z/PDOS-generic in order to prove the concept. Then reevaluate. BFN. Paul. |
|
pdld
This has only just started working, so there may still be issues,
but the linker pdld.exe has now been proven to be able to create an unloaded DOS/VS phase - offline - ie on Windows. The code is C90-compliant so should work anywhere, including VSE itself. I am planning on using the minimal possible assembler to get PDPCLIB operational - as a precursor to doing the same on CMS and MVS. And this is also the precursor to getting z/PDOS-generic to operate as a mini VSE clone similar to how PDOS-generic currently acts as a mini Amiga clone. That will require a modification to sapstart.asm to allow forwarding of SVCs to the C code. Although another way is to avoid doing the SVC calls entirely and get the VSE program to detect that it is running under an SVC-less environment and switch to doing callbacks for the SVC routine is possible. Regardless, going forward, almost everything will be in C instead of assembler, unless I'm missing something fundamental. Before you say - all the interfaces are designed as assembler macros - you need to use assembler just like on MSDOS - well - just like MSDOS, you can have C wrappers for those APIs and they all end up as calls to int86x which is the only thing that needs to be written in assembler. If you look at the MSDOS 4 source that Microsoft released, you can see that they actually did that for MSDOS - they created functions like DosWrite() very similar but not identical to OS/2 DosWrite() - but apparently didn't want people to have this C interface to MSDOS and wanted them to use OS/2 instead. To do it offline, you need an assembler too. That is from a forked binutils 2.14a, ie gas, and I call it as370.exe. Both pdld.exe and as370.exe are in the "dos" directory of the VHD available from pdos.zip at (look where it says "hard drive image"). They are both Windows programs meaning you can run them under real Windows or PDOS/386 (which is effectively a mini-clone of Windows unless you want to quibble about the definition of "mini", quibble about the definition of "clone", quibble about the definition of "Windows", or quibble about the definition of "of" - you know who you are and you have way too much free time). as370.exe produces ELF. pdld.exe accepts as input either ELF or standard object code as produced by the DOS/VS assembler (and then punched - that's why I was asking how to punch object code). And you can mix them. The linker will match lowercase hello_there in an ELF object to HELLO@TH in DOS/VS object file. Note that punching a phase for transportation (similar to doing an IEBCOPY unload on MVS) produces a fully-resolved object file and it is this that pdld outputs. In fact, pdld outputs for MVS too, and it is in fact an IEBCOPY unload too (quibbling aside). So you need to process that using LNKEDT to put it in the CIL (or some equivalent for z/VSE or VSEn). The assembler as370 is only semi-hlasm-compatible. You can see what the assembler code looks like here: and I test it by running this: which runs on VSE/380 (note that the documentation is wrong and the VSE380 environment variable should point to c:\vse380\run or whatever - add the "run"), but it should be simple enough to adjust for whatever VS or VSE environment you are using. The program as it currently stands just has an assembler program calling a C function that returns 6 in R15 and then the assembler goes into a loop so that you can see that in Hercules by pressing ESC. I'll switch it to do something WTO-like in the future and then expand until I have a new version of PDPCLIB almost entirely in C. And have z/PDOS-generic updated each step of the way. Note that there is no barrier to making as370 more hlasm-compatible and also I am thinking I might use the C preprocessor to have conditional assembly so that both the DOS/VS assembler and as370 can handle it while waiting for that to happen. Note that I am having fun probing the "new" environment from the safety of a C compiler and securing one thing at a time in C. BFN. Paul. |
|
Re: dumping object code
So lemme show ?ya ... // ASSGN SYS007,SYSPCH? <---- job life assignment of SYS007 to the POWER punch // ASSGN SYS000,SYSLNK <---- job life assignment of SYS000 to SYSLNK ... // DLBL IJSYSPH,'FUNC2.OBJ',0,SD ?<------ Assign SYSPCH?to a disk file // EXTENT SYSPCH,,,,12000,500 SPACE-OBJ ASSGN SYSPCH,SYS000 <----- Perm assignment of SYSPCH?to SYS000 ... So you have it set up as: SYSPCH?> SYS000 > SYSLNK ... The right way to do this is: // DLBL IJSYSPH,'FUNC2.OBJ',0,SD ?<------ Assign SYSPCH?to a disk file // EXTENT SYSPCH,,,,12000,500 SPACE-OBJ // ASSGN SYSPCH,SYSLNK Joe On Sun, Sep 8, 2024 at 6:23?AM Paul Edwards via <mutazilah=[email protected]> wrote: On Sat, Sep? 7, 2024 at 08:44 PM, Joe Monk wrote: |
|
Re: dumping object code
On Sat, Sep 7, 2024 at 08:44 PM, Joe Monk wrote:
So setup all your logicals at the beginning of the job, and only changeI got an error when I tried adding // to my ASSGNs, but I have since managed to figure out how to dump object code, one at a time, via separate JCL below. So now hopefully the pdld author will be able to support VS(E) as a target. To be combined with as370 as the assembler, and gcc370 as the C compiler. So that executables suitable for running on DOS/VS as well as z/VSE and VSEn can be built on Windows. BFN. Paul. * $$ JOB JNM=VSEJOB * $$ LST LST=SYSLST,CLASS=A // JOB VSEJOB * * * * Standard assignments for C programs * // ASSGN SYS000,SYSLNK // ASSGN SYS005,SYSLST // ASSGN SYS007,SYSPCH // OPTION DUMP * * * * * * * Now assemble the main routine * // DLBL IJSYSPH,'FUNC2.OBJ',0,SD // EXTENT SYSPCH,,,,12000,500 SPACE-OBJ ASSGN SYSPCH,SYS000 // OPTION DECK,NOEDECK // EXEC ASSEMBLY undivert(func2.asm)dnl /* CLOSE SYSPCH,PUNCH * * * * // DLBL SDI1,'FUNC2.OBJ' // TLBL MTO1,'HERC01.MFTOPC',0 // ASSGN SYS011,TAPE,VOL=MFTOPC // EXEC VSEMANIP,SIZE=AUTO,PARM='dd:sdi1 dd:mto1' * * * /& * $$ EOJ |
René Ferland
to navigate to use esc to dismiss