Re: RCFs (was Valid hexadecimal (was: EBCDIC to HEX translation in Assembler?))
Patrick O'Keefe wrote: [...] I've noticed that some recent IBM manuals (maybe only Tivoli manuals, but still IBM) no longer include the RCF or any electronic equivalent. Is there an IBM-wide RCF (where F now stands for function) that can be used for those manuals not providing their own? If so, I've not found it (but haven't searched much, either). I always use e-mail (mhvrcfs aatt us.ibm.com) for submitting comments, despite it is Tivoli or other IBM brand. It works. -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237 NIP: 526-021-50-88 Wedug stanu na dzie 01.01.2007 r. kapita zakadowy BRE Banku SA (w caoci opacony) wynosi 118.064.140 z. W zwizku z realizacj warunkowego podwyszenia kapitau zakadowego, na podstawie uchwa XVI WZ z dnia 21.05.2003 r., kapita zakadowy BRE Banku SA moe ulec podwyszeniu do kwoty 118.760.528 z. Akcje w podwyszonym kapitale zakadowym bd w caoci opacone. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: RCFs (was Valid hexadecimal (was: EBCDIC to HEX translation in Assembler?))
You're off the hook, and if you've yet taken no action, it would be interesting to let it run its course and see whether Tech Pubs agrees with us. The way our ID process seems to work today (at least in Poughkeepsie), if someone suggests a change, the book owner contacts the technical owner to see if (s)he agrees. So the ID person is not doing the agreeing. I've also been informed that, to my dismay, no updates will happen to any old books ever. Updates will be made only in the forthcoming R9 books. I've noticed that some recent IBM manuals (maybe only Tivoli manuals, but still IBM) no longer include the RCF or any electronic equivalent. Is there an IBM-wide RCF (where F now stands for function) that can be used for those manuals not providing their own? If so, I've not found it (but haven't searched much, either). Ugghh. The z/OS MVS books (i.e., the ones I am involved with) all have a page at the end Readers' Comments -- We'd Like to Hear from You. I'm not sure why there is no electronic mechanism. I'll inquire. But that is not consistent across the z/OS elements, unfortunately. I'll ask about that too. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: RCFs (was Valid hexadecimal (was: EBCDIC to HEX translation in Assembler?))
Peter Relson wrote on 2007-07-25 07:39:42: snip Ugghh. The z/OS MVS books (i.e., the ones I am involved with) all have a page at the end Readers' Comments -- We'd Like to Hear from You. I'm not sure why there is no electronic mechanism. I'll inquire. But that is not consistent across the z/OS elements, unfortunately. I'll ask about that too. I found the following in the front matter of several books from the z/OS MVS bookshelf: -- IBM welcomes your comments. A form for readers’ comments may be provided at the back of this document, or you may address your comments to the following address: International Business Machines Corporation Department 55JA, Mail Station P384 2455 South Road Poughkeepsie, NY 12601-5400 United States of America FAX (United States Canada): 1+845+432-9405 FAX (Other Countries): Your International Access Code +1+845+432-9405 IBMLink™ (United States customers only): IBMUSM10(MHVRCFS) Internet e-mail: [EMAIL PROTECTED] World Wide Web: www.ibm.com/servers/eserver/zseries/zos/webqs.html If you would like a reply, be sure to include your name, address, telephone number, or FAX number. Make sure to include the following in your comment or note: v Title and order number of this document v Page number or topic related to your comment When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. - My personal favorite, used often, is the internet e-mail address. There is a good, disciplined process to ensure that the comments get responses. I don't have an answer regarding publications from other elements of z/OS, but I'll look in tandem with Peter. Bob Wright - MVS Service Aids
Re: RCFs (was Valid hexadecimal (was: EBCDIC to HEX translation in Assembler?))
I wrote on 2007-07-25 08:19:01: I found the following in the front matter of several books from the z/OS MVS bookshelf: -- IBM welcomes your comments. A form for readers’ comments may be provided at the back of this document, or you may address your comments to the following address: International Business Machines Corporation Department 55JA, Mail Station P384 2455 South Road Poughkeepsie, NY 12601-5400 United States of America FAX (United States Canada): 1+845+432-9405 FAX (Other Countries): Your International Access Code +1+845+432-9405 IBMLink™ (United States customers only): IBMUSM10(MHVRCFS) Internet e-mail: [EMAIL PROTECTED] World Wide Web: www.ibm.com/servers/eserver/zseries/zos/webqs.html If you would like a reply, be sure to include your name, address, telephone number, or FAX number. Make sure to include the following in your comment or note: v Title and order number of this document v Page number or topic related to your comment When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. I found identical information in TSO/E, DFSMS, and DFSORT books. ISPF books carry similar statements, but they invite responses to [EMAIL PROTECTED] Look just inside the front cover of recent books for invitations to supply feedback electronically. Bob Wright - MVS Service Aids
Re: RCFs (was Valid hexadecimal (was: EBCDIC to HEX translation in Assembler?))
On Wed, 25 Jul 2007 07:39:42 -0400, Peter Relson wrote: I've also been informed that, to my dismay, no updates will happen to any old books ever. Updates will be made only in the forthcoming R9 books. For the matter that started this thread, that FIN-analogue is sufficient. Of course, if the update is sufficiently urgent, such as removing a mention of Hercules, there will be a deviation from the policy. Ugghh. The z/OS MVS books (i.e., the ones I am involved with) all have a page at the end Readers' Comments -- We'd Like to Hear from You. I'm not sure why there is no electronic mechanism. I'll inquire. It would be useful if the HTML (at least) version of the Comments page contained a URL such as: mailto://[EMAIL PROTECTED] ... but perhaps that's a topic for another (global) RCF. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Valid hexadecimal (was: EBCDIC to HEX translation in Assembler?)
Minor chide: It is too bad that folks take their valuable time on ibm-main to point out deficiencies in the documentation (pointing out is a good thing) but then do not submit requests to get them updated. The reason we in IBM follow and participate in ibm-main is not for the purpose of seeing what pub updates are being suggested. Please help! The meaning would be clearer if the two adjectives were omitted and it simply said any character. I agree with the suggestion and will check into getting it changed. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Valid hexadecimal (was: EBCDIC to HEX translation in Assembler?)
On Tue, 24 Jul 2007 07:28:52 -0400, Peter Relson wrote: Minor chide: It is too bad that folks take their valuable time on ibm-main Cf. the Heresy thread. to point out deficiencies in the documentation (pointing out is a good thing) but then do not submit requests to get them updated. The reason we Chiding accepted and RCF submitted against R8 rather than R7, and mentioning 3 other publications in which a string search turned up similar usage. in IBM follow and participate in ibm-main is not for the purpose of seeing what pub updates are being suggested. Please help! But some assessment from my peers (IBM and customers) helps me decide whether my observations are valid. The meaning would be clearer if the two adjectives were omitted and it simply said any character. I agree with the suggestion and will check into getting it changed. You're off the hook, and if you've yet taken no action, it would be interesting to let it run its course and see whether Tech Pubs agrees with us. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
RCFs (was Valid hexadecimal (was: EBCDIC to HEX translation in Assembler?))
On Tue, 24 Jul 2007 11:04:35 -0500, Paul Gilmartin [EMAIL PROTECTED] wrote: ... Minor chide: It is too bad that folks take their valuable time on ibm- main Cf. the Heresy thread. Ah, but that thread allowed us to streach our pedantry muscles, an invaluable service for system programmers. ... Chiding accepted and RCF submitted ... ... I've noticed that some recent IBM manuals (maybe only Tivoli manuals, but still IBM) no longer include the RCF or any electronic equivalent. Is there an IBM-wide RCF (where F now stands for function) that can be used for those manuals not providing their own? If so, I've not found it (but haven't searched much, either). Pat O'Keefe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Valid hexadecimal (was: EBCDIC to HEX translation in Assembler?)
On Mon, 23 Jul 2007 08:23:38 -0600, Steve Comstock wrote: Depends what you mean. x'FACE' is a hexadecimal number, right? (= 64206 in decimal, if an unsigned number). c'FACE' is one way of representing it in EBCDIC So you want to convert c'FACE' to x'FACE'? Or are you talking zoned decimal, packed decimal, or floating point numbers? Give us some info on the parameters that bound your problem. There's a pervasive ambiguous and careless usage in this area. One of my favorite (not!) examples is: Title: z/OS V1R7.0 MVS Assembler Services Reference ABE-HSP Document Number: SA22-7606-07 91.0 ENQ -- Request Control of a Serially Reusable Resource * 91.1 Description 91.1.8 Parameters qname addr Specifies the address of an 8-character name. The name can contain any valid hexadecimal character. ... OK. The adjectives valid and hexadecimal appear to be restrictive -- It's pretty hard to expand the scope of any. I'd infer that some characters are not valid, and the qname can not contain them. Where are the valid characters enumerated? Are they the same as the characters called valid in the JCL manuals? And does the use of hexadecimal imply that the only characters which the qname may contain are '0', '1', '2', '3', '4', '5', '6', '7', '8', '9', 'A', 'B', 'C', 'D', 'E', and 'F'? Or that the addressed qname must be expressed in assembler language as a hexadecimal self-defining term? The meaning would be clearer if the two adjectives were omitted and it simply said any character. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Valid hexadecimal (was: EBCDIC to HEX translation in Assembler?)
On Mon, 23 Jul 2007 10:24:12 -0500, Paul Gilmartin [EMAIL PROTECTED] wrote: On Mon, 23 Jul 2007 08:23:38 -0600, Steve Comstock wrote: Depends what you mean. x'FACE' is a hexadecimal number, right? (= 64206 in decimal, if an unsigned number). c'FACE' is one way of representing it in EBCDIC So you want to convert c'FACE' to x'FACE'? Or are you talking zoned decimal, packed decimal, or floating point numbers? Give us some info on the parameters that bound your problem. There's a pervasive ambiguous and careless usage in this area. One of my favorite (not!) examples is: Title: z/OS V1R7.0 MVS Assembler Services Reference ABE-HSP Document Number: SA22-7606-07 91.0 ENQ -- Request Control of a Serially Reusable Resource * 91.1 Description 91.1.8 Parameters qname addr Specifies the address of an 8-character name. The name can contain any valid hexadecimal character. ... OK. The adjectives valid and hexadecimal appear to be restrictive -- It's pretty hard to expand the scope of any. I'd infer that some characters are not valid, ... The meaning would be clearer if the two adjectives were omitted and it simply said any character. ... Better written documentation points to a code page or other specific definition of valid character. In any case, the word hexadecimal as they used it makes no sense. Binary would have been just as meaningful (or meaningless). Pat O'Keefe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
