开云体育

I though I was really confused and now I know I am, not only are there CKD, and CCKD, but also HDR-30 disk images, and also an AWSCKD disk image. What are these used for? Very little information online about these. I didn’t get any answers in H390-Herc so I’m going to try here. Thanks in advance.

Hi, Just a note to say that the REVIEW /RFE package is now up to release 51.3 and can be downloaded from https://www.prycroft6.com.au/REVIEW/index.html The main new features of release 51 for the REVIEW browser are: Auto-RECEIVE when browsing an XMIT which presents an un-xmitted copy of the data in a temporary data set - this can be suppressed by the DATA operand or the slash (/) selection code, as appropriate. The new ZOOM command to zoom-in to a single record - use END to back out to the multi-record view. While ZOOM may be better for some long records than HEX, HEXR and HEXX for general browsing, the main purpose of ZOOM is to allow the examination of individual fields of SMF records. To this end a new (large) module called REVSMFZ is now shipped which contains knowledge of the structure of numerous types (and subtypes) of SMF records. When a record with a structure is recognised by ZOOM, the fields of the various record sections will be broken out and displayed below the item name. With R51.3, a smaller module named REVSMF7 is used for MVS/370 (and pre-MVS in some cases) SMF record structure knowledge. Because the item name is shown, if you know the name of a field of particular interest, you can use FIND to quickly locate it in the data display. If you press <enter> when the cursor is over the name of an item (usually shown in red on the screen), the commentary for that item will be shown. Press <enter> again to clear the commentary. Since one of the aims was to reduce the need to scroll right for long records, the fields will generally be formatted to appear in the left-most screen-width of the display. An exception to this is for repeated sections (such as DD I/O sections from types 4, 34 and 30) where longer records may be used so that sections instances can be shown aligned on consecutive records under a single occurrence of the relevant item names. The decimal representation of 16-bit binary, 64-bit binary and long floating point has only been fixed at the 51.3 level. If you want to preserve the display, you can use the CUT command to copy some or all of the ZOOM view records to an existing or new data set. To copy the whole thing, simply issue CUT while viewing the top of the data. In terms of SMF record type coverage, most of the interesting pre-MVS/SE records are catered for apart from those from MF/1. REVSMF7 even has data for the the type 1 (OS wait time) and type 30 (start time sharing) pre-MVS records such as are produced by SVS (but may actually be older than SVS). For z/OS, REVSMFZ has data for many original MVS records plus types 30, 41, 42, 89 and RMF types 70, 71 and 72. Also, many MVS record types have new sections in later OS levels which are also handled. Not all subtypes of supported record types with subtypes may be fully supported. The SMF "knowledge" is based on assembler DSECTs of SMF record sections, so in theory if there is assembler source for an SMF record that is known to always be a specific record type (and subtype where applicable) then it should be able to be added to this scheme. In fact, this scheme could also be extended to non-SMF records (either instead or in addition to) if the relevant filter tables were coded up. Support for many obvious non-MVS records (more RMF records, network products NPDA and NLDM, CICS (apart from the base and product sections), DB2, etc) is not present because either I could not find suitable assembler source code for the structures or I do not have access to sample data with which to debug the formatting. As always, bug reports are welcome. If you have any particular SMF record types and/or subtypes for which you have structure source and sample data that you'd like to see added, feel free to donate the necessary inputs. Cheers, Greg

Hi folks. I'm on Tk5, and I'm trying to learn how to mess with dataset member records from COBOL. After some early successes on getting the compiler happy with accesing the dataset member itself (which has not been straightforward either) I'm getting to the point where I can't progress any longer. Now I'm just trying to simply print 'hello world' on output as a 'proof of iteration', while trying a PERFORM loop on the records of a member. The compiler COB step ends with code 0004 (LKED and GO got both 0000), and a pair of IKF warning error cards are printed (which I'm unable to find on any IBM book around) and the program just does nothing: IKF1043I-W END OF SENTENCE SHOULD PRECEDE END OF PROGRAM . ASSUMED PRESENT. IKF4072I-W EXIT FROM PERFORMED PROCEDURE ASSUMED BEFORE PROCEDURE-NAME . While the actual code looks like this: 000-ITERATE. OPEN INPUT IPBLKFILE. READ IPBLKFILE AT END MOVE HIGH-VALUES TO IPBLKDETAILS PERFORM 001-DISPLAY UNTIL IPBLKDETAILS = HIGH-VALUES CLOSE IPBLKFILE. STOP RUN. 001-DISPLAY. DISPLAY HELLO-CONST UPON CNSL. READ IPBLKFILE AT END MOVE HIGH-VALUES TO IPBLKDETAILS I'm really struggling with finding whether periods and closing statements such as END-READ, etc, have to be in place around (fought my way to here often by sheer try/error) since the 70s compiler on MVS seems to be quite different to most information I'm finding googling around. But now nothing seems to work. So I feel I'm missing semething else here. Any clues? Thanks.