Re: Automated DDR funny - has anyone got any ideas

[Brian Nielsen]

On Sat, 13 Mar 2010 08:52:35 -0500, Alan Altmark  
wrote:

>The standard defines "alphabetic" as A-Z (actually, A, B, C, D, etc. to
>avoid confusion) and "numeric" as 0-9.
>
>So, our existing labeling programs that allow blanks in the middle of
>labels (very annoying) and characters that aren't the same in all code
>pages (@ is one) are permitted under the grandfather clause, but they
>aren't compliant.

It is interesting to compare the documentation for what is allowed by 
ICKDSF, CPFMTXA, and the CMS FORMAT command.

 ICKDSF: "1 to 6 alphanumeric characters"

 CPFMTXA: "1-character to 6-character name. (The characters need not be 

alphanumeric.) Embedded blanks are not allowed."

 CMS FORMAT: "one to six numeric (0-9) or alphabetic (A-Z) characters, or
 
both." and "Note: Special characters, such as “(” or ‘’ (blank) a
re valid 
in a label with FORMAT, but may not be valid in other VM commands."

Brian Nielsen

Re: Automated DDR funny - has anyone got any ideas

[Schuh, Richard]

I got that from a different IBM manual. The so called  national characters have 
been a part of the alphanumeric set since S/360 days. They were included as an 
extension of the alphabet. 

http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzatb/vdefn.htm
IBM standard volume label (VOL1)
" The alphanumeric character set includes A-Z, 0-9, @, $, and #. "

Regards, 
Richard Schuh 

 

> -Original Message-
> From: The IBM z/VM Operating System 
> [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark
> Sent: Saturday, March 13, 2010 5:53 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: Automated DDR funny - has anyone got any ideas
> 
> On Friday, 03/12/2010 at 05:42 EST, "Schuh, Richard" 
> wrote:
> > It must be Friday, Alan answered hastily like he was 
> anxious to leave
> the 
> > office. It is A-Z, 0-9, @,#,$
> 
> Alan did not answer hastily.  From IBM Corporate Standard C-S 
> 3-8010-003, 1998, "Volume Labels for Storage Devices":
> 
> "This field may
> contain from one to six alphabetic and/or numeric characters. 
> If the volume identifier is less than six characters, it is 
> left-justified and the remainder is padded with spaces. On 
> both input and output, the system must check this field 
> against the value supplied by the user. The content is 
> permanently assigned by the installation to identify this 
> volume, and is entered at label creation.
> Note: Some existing systems accept a wider character set than 
> is permitted here, if the characters are specified within 
> enclosing apostrophes. Some programs to which this standard 
> is applicable must maintain compatibility with these systems 
> and are therefore permitted this specific additional latitude."
> 
> The standard defines "alphabetic" as A-Z (actually, A, B, C, 
> D, etc. to avoid confusion) and "numeric" as 0-9.
> 
> So, our existing labeling programs that allow blanks in the 
> middle of labels (very annoying) and characters that aren't 
> the same in all code pages (@ is one) are permitted under the 
> grandfather clause, but they aren't compliant.
> 
> Alan Altmark
> z/VM Development
> IBM Endicott
> 

Re: Automated DDR funny - has anyone got any ideas

[Alan Altmark]

On Friday, 03/12/2010 at 05:42 EST, "Schuh, Richard"  
wrote:
> It must be Friday, Alan answered hastily like he was anxious to leave 
the 
> office. It is A-Z, 0-9, @,#,$

Alan did not answer hastily.  From IBM Corporate Standard C-S 3-8010-003, 
1998, "Volume Labels for Storage Devices":

"This field may
contain from one to six alphabetic and/or numeric
characters. If the volume identifier is less than six
characters, it is left-justified and the remainder is
padded with spaces. On both input and output,
the system must check this field against the value
supplied by the user. The content is permanently
assigned by the installation to identify this volume,
and is entered at label creation.
Note: Some existing systems accept a wider character
set than is permitted here, if the characters
are specified within enclosing apostrophes. Some
programs to which this standard is applicable must
maintain compatibility with these systems and are
therefore permitted this specific additional latitude."

The standard defines "alphabetic" as A-Z (actually, A, B, C, D, etc. to 
avoid confusion) and "numeric" as 0-9.

So, our existing labeling programs that allow blanks in the middle of 
labels (very annoying) and characters that aren't the same in all code 
pages (@ is one) are permitted under the grandfather clause, but they 
aren't compliant.

Alan Altmark
z/VM Development
IBM Endicott

Re: Automated DDR funny - has anyone got any ideas

[Schuh, Richard]

It must be Friday, Alan answered hastily like he was anxious to leave the 
office. It is A-Z, 0-9, @,#,$

Regards, 
Richard Schuh 

 

> -Original Message-
> From: The IBM z/VM Operating System 
> [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark
> Sent: Friday, March 12, 2010 2:32 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: Automated DDR funny - has anyone got any ideas
> 
> On Thursday, 03/11/2010 at 05:39 EST, Brian Nielsen 
>  wrote:
> > The main problem to solve is still the same as the original posters'
> > problem: The DASD label might contain the special characters or
> character
> > 
> > DASD labels of @@, ¢¢, and /* */ are all valid
> 
> Sorry if I'm being unclear.  If you put a comment delimiter 
> anywhere prior to the end of a statement, it is a syntax 
> error, not a comment.
> 
>   OUTPUT 111 3390 ; comment
> 
> would not interpret the semicolon as a volid.
> 
> And while the characters you list are allowed, they are not 
> valid.  The IBM VOL1 label standard defines the label to be 
> A-Z and 0-9.  It permits other characters for compatibility, 
> but only when placed within a quoted 
> string.   I know, I know: if no one follows it, it must not 
> be much of a 
> Standard, wot?
> 
> Alan Altmark
> z/VM Development
> IBM Endicott
> 

Re: Automated DDR funny - has anyone got any ideas

[Alan Altmark]

On Thursday, 03/11/2010 at 05:39 EST, Brian Nielsen 
 wrote:
> The main problem to solve is still the same as the original posters'
> problem: The DASD label might contain the special characters or 
character
> 
> DASD labels of @@, ¢¢, and /* */ are all valid 

Sorry if I'm being unclear.  If you put a comment delimiter anywhere prior 
to the end of a statement, it is a syntax error, not a comment.

  OUTPUT 111 3390 ; comment

would not interpret the semicolon as a volid.

And while the characters you list are allowed, they are not valid.  The 
IBM VOL1 label standard defines the label to be A-Z and 0-9.  It permits 
other characters for compatibility, but only when placed within a quoted 
string.   I know, I know: if no one follows it, it must not be much of a 
Standard, wot?

Alan Altmark
z/VM Development
IBM Endicott

Re: Automated DDR funny - has anyone got any ideas

[Schuh, Richard]

You already have parsers that know how to parse REXX comments, so the 
complexity is not that tough to deal with. However, it does require that the 
person updating or creating the file be more careful and, perhaps, use QDI if 
building by hand.

Because of the possibility of having special characters in volsers, it would be 
appropriate to require that comments, however delimited, be isolated 
statements. The complexity is in determining whether what follows the presumed 
delimiter is data or comment. That would be avoided by not allowing comments on 
the command statements. It would also be easier to add to the current code - a 
single check to determine whether it is a comment.

Regards, 
Richard Schuh 

 

> -Original Message-
> From: The IBM z/VM Operating System 
> [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark
> Sent: Thursday, March 11, 2010 1:58 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: Automated DDR funny - has anyone got any ideas
> 
> On Thursday, 03/11/2010 at 03:19 EST, "Daniel P. Martin" 
>  wrote:
> > Well,  yes, the semicolon does work...  but if you're going 
> to have to 
> > do new work to hack the way DDR parses statements anyhow, REXX-ish 
> > syntax would certainly be a desirable approach.  Not that I 
> have any 
> > delusions about the development process being at all 
> democratic, but 
> > if you're considering votes, I vote for:
> > 
> > - "/* blah blah blah */" syntax for comments
> > - ";" (semicolon) for statement continuation
> 
> Ooooh.  Humpty Dumpty strikes again!  You have cleverly 
> changed the definition of "desirable" to mean "the most 
> complicated option possible". 
> REXX comments.  Nesting.  
> 
> Semicolons, otoh, are simple to describe and simple to implement.
> 
> Alan Altmark
> z/VM Development
> IBM Endicott
> 

Re: Automated DDR funny - has anyone got any ideas

[Mark Post]

>>> On 3/11/2010 at 05:47 PM, "Daniel P. Martin"  
>>> wrote: 
> Yeah.  I know.  Somewhere next week, in Seattle, when I least expect it, 
> I will pay.

Just being in Seattle isn't punishment enough?  I vote for clemency.


Mark Post

Re: Automated DDR funny - has anyone got any ideas

[Daniel P. Martin]

Oh.  I'm sorry.  I didn't realize you had wandered down the primrose 
path of thinking I was trying to suggest what some might call the "easy" 
solution... :-p


Yeah.  I know.  Somewhere next week, in Seattle, when I least expect it, 
I will pay.


*sigh*

-dan.

On 3/11/2010 3:58 PM, Alan Altmark wrote:

On Thursday, 03/11/2010 at 03:19 EST, "Daniel P. Martin"
  wrote:
   

Well,  yes, the semicolon does work...  but if you're going to have to
do new work to hack the way DDR parses statements anyhow, REXX-ish
syntax would certainly be a desirable approach.  Not that I have any
delusions about the development process being at all democratic, but if
you're considering votes, I vote for:

- "/* blah blah blah */" syntax for comments
- ";" (semicolon) for statement continuation
 

Ooooh.  Humpty Dumpty strikes again!  You have cleverly changed the
definition of "desirable" to mean "the most complicated option possible".
REXX comments.  Nesting.

Semicolons, otoh, are simple to describe and simple to implement.

Alan Altmark
z/VM Development
IBM Endicott
   

Re: Automated DDR funny - has anyone got any ideas

[Brian Nielsen]

On Thu, 11 Mar 2010 16:43:14 -0500, Alan Altmark  
wrote:

>If I ran the zoo, I would propose that DDR
>- no longer check for @
>- continue to obey Ý as it does today.
>- add an actual comment capability

The main problem to solve is still the same as the original posters' 
problem: The DASD label might contain the special characters or character
 
sequences.  DASD labels of @@, ¢¢, and /* */ are all 
valid and may 
trip up a syntax that allows comments on the same line as non-comment 
statements.  I'd strip out checking for the cent sign too and go only wit
h 
full line comments.  Perhaps a new DDR statement called COMMENT would be 

appropriate and obvious.

Brian Nielsen

Re: Automated DDR funny - has anyone got any ideas

[Alan Altmark]

On Thursday, 03/11/2010 at 03:19 EST, "Daniel P. Martin" 
 wrote:
> Well,  yes, the semicolon does work...  but if you're going to have to
> do new work to hack the way DDR parses statements anyhow, REXX-ish
> syntax would certainly be a desirable approach.  Not that I have any
> delusions about the development process being at all democratic, but if
> you're considering votes, I vote for:
> 
> - "/* blah blah blah */" syntax for comments
> - ";" (semicolon) for statement continuation

Ooooh.  Humpty Dumpty strikes again!  You have cleverly changed the 
definition of "desirable" to mean "the most complicated option possible". 
REXX comments.  Nesting.  

Semicolons, otoh, are simple to describe and simple to implement.

Alan Altmark
z/VM Development
IBM Endicott

Re: Automated DDR funny - has anyone got any ideas

[Schuh, Richard]

Boy, is that old.

Regards, 
Richard Schuh 

 

>  Most often, the default values for these two symbols are 
> defined for each 
>  
>  virtual machine at system generation. When you use the CP 
> TERMINAL command to  redefine the CHARDEL and LINEDEL 
> characters, the redefinitions have no effect  on DDR line 
> editing. DDR continues to recognize the at sign (@) and the 
> cent  sign (Ý) as valid CHARDEL and LINEDEL symbols, respectively.
> 
> With CP you can enter
>  ignore this Ý Q time
> 
> If I ran the zoo, I would propose that DDR
> - no longer check for @
> - continue to obey Ý as it does today.
> - add an actual comment capability
> 
> Alan Altmark
> z/VM Development
> IBM Endicott
> 

Re: Automated DDR funny - has anyone got any ideas

[Alan Altmark]

On Thursday, 03/11/2010 at 03:23 EST, Brian Nielsen 
 wrote:
> The version with the cent sign in the middle of the line does not work 
as
> you are expecting.  A cent sign anywhere in the line discards the entire
> line, not just what is before it.

So, contrary to the doc, it isn't really a LINEDEL.

>From the HELP:
  The first is the logical character-delete symbol (@) that allows 
 deletion of one or more of the previous characters entered. The second is 
the 
 logical-line delete symbol (Ý) that deletes the entire previous physical 
line.
 Most often, the default values for these two symbols are defined for each 
 
 virtual machine at system generation. When you use the CP TERMINAL 
command to 
 redefine the CHARDEL and LINEDEL characters, the redefinitions have no 
effect 
 on DDR line editing. DDR continues to recognize the at sign (@) and the 
cent 
 sign (Ý) as valid CHARDEL and LINEDEL symbols, respectively.

With CP you can enter
 ignore this Ý Q time

If I ran the zoo, I would propose that DDR
- no longer check for @
- continue to obey Ý as it does today.
- add an actual comment capability

Alan Altmark
z/VM Development
IBM Endicott

Re: Automated DDR funny - has anyone got any ideas

[Brian Nielsen]

On Thu, 11 Mar 2010 14:21:07 -0500, Alan Altmark  
wrote:

>Semicolon works ok as it allows
>  INPUT 181 TAPE ( LEAVE ;  Comment on the same line
>and
>  ; Full line comment
>
>
>Today you have to code
> Comment on same line   ¢INPUT 181 TAPE ( LEAVE
>and
>   Full line comment ¢


The version with the cent sign in the middle of the line does not work as
 
you are expecting.  A cent sign anywhere in the line discards the entire 

line, not just what is before it.  Here some output from one of several 

tests:


type comtest ddrcntrl a

SYSPRINT CONS
this is a comment ¢INPUT 191 DASD
OUTPUT 1002 DASD
COPY ALL

Ready; T=0.01/0.01 13:18:38
ddr comtest ddrcntrl a
HCPDDR708E INVALID INPUT OR OUTPUT DEFINITION
END OF JOB
Ready(2); T=0.01/0.01 13:18:40


Whether the fault is with the documentation or with the code is up to you
.

Brian Nielsen

Re: Automated DDR funny - has anyone got any ideas

[Daniel P. Martin]

Well,  yes, the semicolon does work...  but if you're going to have to 
do new work to hack the way DDR parses statements anyhow, REXX-ish 
syntax would certainly be a desirable approach.  Not that I have any 
delusions about the development process being at all democratic, but if 
you're considering votes, I vote for:


- "/* blah blah blah */" syntax for comments
- ";" (semicolon) for statement continuation

-dan.

On 3/11/2010 1:21 PM, Alan Altmark wrote:

On Thursday, 03/11/2010 at 12:16 EST, Brian Nielsen
  wrote:

   

If you were inclined to add an official comment syntax to DDR control
files I would suggest using REXX style comments as are also used in
 

SYSTEM
   

CONFIG.  I suppose another choice could be the semi-colon as used by
 

TCPIP.

Semicolon works ok as it allows
   INPUT 181 TAPE ( LEAVE ;  Comment on the same line
and
   ; Full line comment


Today you have to code
  Comment on same line   ¢INPUT 181 TAPE ( LEAVE
and
Full line comment ¢

Alan Altmark
z/VM Development
IBM Endicott
   

Re: Automated DDR funny - has anyone got any ideas

[Alan Altmark]

On Thursday, 03/11/2010 at 12:16 EST, Brian Nielsen 
 wrote:

> If you were inclined to add an official comment syntax to DDR control
> files I would suggest using REXX style comments as are also used in 
SYSTEM
> CONFIG.  I suppose another choice could be the semi-colon as used by 
TCPIP.

Semicolon works ok as it allows
  INPUT 181 TAPE ( LEAVE ;  Comment on the same line
and
  ; Full line comment


Today you have to code
 Comment on same line   ¢INPUT 181 TAPE ( LEAVE
and
   Full line comment ¢

Alan Altmark
z/VM Development
IBM Endicott

Re: Automated DDR funny - has anyone got any ideas

[Brian Nielsen]

On Thu, 11 Mar 2010 08:49:46 -0500, Alan Altmark  
wrote:

>On Thursday, 03/11/2010 at 06:44 EST, Ivica Brodaric
> wrote:
>> So, we will all now suffer a brand new control statement because of yo
u.
>;-)
>
>I don't mind leaving the cent sign as a comment prefix delimiter (not as
 a
>"line delete") for compatibility, but we'll want another standard symbol

>as well (e.g. >) so that the rest of us who don't have the cent sign in
>their code page can use it, too.


Actually, I use it as a suffix.  Here is a real example extracted from a 

file built by my automated DDR backup process:

INPUT 181 TAPE ( LEAVE
OUTPUT 6427 DASD VM6427
RESTORE 0 to 3338
** DASD volume VM6428 spans tape boundary ¢
** Next tape is VM0154 ¢
INPUT 181 TAPE ( LEAVE
OUTPUT 6428 DASD VM6428
RESTORE 0 to 3338


The "comment" lines were inserted as part of the processing when the firs
t 
tape reached EOV.

If you were inclined to add an official comment syntax to DDR control 
files I would suggest using REXX style comments as are also used in SYSTE
M 
CONFIG.  I suppose another choice could be the semi-colon as used by TCPI
P.

Brian Nielsen

Re: Automated DDR funny - has anyone got any ideas

[Alan Altmark]

On Thursday, 03/11/2010 at 06:44 EST, Ivica Brodaric 
 wrote:
> So, we will all now suffer a brand new control statement because of you. 
;-) 

I don't mind leaving the cent sign as a comment prefix delimiter (not as a 
"line delete") for compatibility, but we'll want another standard symbol 
as well (e.g. >) so that the rest of us who don't have the cent sign in 
their code page can use it, too.

Alan Altmark
z/VM Development
IBM Endicott

Re: Automated DDR funny - has anyone got any ideas

[Ivica Brodaric]

>
> I like to use the line delete symbol as a way to add comments to my DDR
> control files.
>

So, we will all now suffer a brand new control statement because of you.
;-)

Re: Automated DDR funny - has anyone got any ideas

[Brian Nielsen]

I like to use the line delete symbol as a way to add comments to my DDR 

control files.

Brian Nielsen

On Wed, 10 Mar 2010 14:07:36 +0100, Colin Allinson 
 wrote:

>I should read the DDR help more carefully next time !!
>
>" When you use the CP TERMINAL command to redefine the CHARDEL and 
LINEDEL 
>characters, the redefinitions have no effect  on DDR line editing. DDR 

>continues to recognize the at sign (@) and the cent  sign (¢) as valid
 
>CHARDEL and LINEDEL symbols, respectively."
>
> 
>
>Colin Allinson
>
>Amadeus Data Processing GmbH
>

Re: Automated DDR funny - has anyone got any ideas

[Colin Allinson]

Mike Walter  wrote :-

> What happens if your control statement volser matches the volser 
reported by DDR, e.g. 
> OUT D5F3 DASD v...@d5f3 

> Is the actual DASD volser being written to really d...@d543, or actually 
v...@d5f3 as reported by DDR? 

Sorry, that was a typo. I should have cut & pasted it. The control 
statement was v...@d5f3 as you have in your append (not d...@d5f3)

The issue was all about the @ functioning as a CHARDEL even when turned 
off in CP TERM (now explained).


Colin Allinson
Amadeus Data Processing GmbH

Re: Automated DDR funny - has anyone got any ideas

[Alan Altmark]

On Wednesday, 03/10/2010 at 09:25 EST, Nick Laflamme 
 wrote:

> I'd be very tempted to open a PMR and "request" they also respect an 
ESCAPE 
> character. It's only fair.
> 
> But that's a long-term solution, not a short-term solution. :-( 

Go ahead and open a PMR.  While it is behaving as documented, it is not 
behaving in accordance with the system design we put in place a few 
releases ago when we changed the default CHARDEL and LINEDEL characters to 
OFF in the IBM-provided SYSTEM CONFIG.

A contributing factor to the demise of the remnants of serial line 
interactions is that code points 0x7C and 0x4A do not always appear as @ 
and ¢, respectively.  On my terminal, I see @ and Ý, as I use code page 
924.  In Brazil (cp275), you see à and É.

Finally, try to explain CHARDEL or LINEDEL to anyone coming out of 
college.  I triple dog dare you.  ("You do that WHY?" and "But there's no 
CENT sign on the keyboard!") At least LINEND is a familiar concept and has 
some practical use as a command delimiter.

On the lighter side, here's a snippet from the code:
*AN '@' SIGN WILL BE TREATED AS A LOGICAL BACKSPACE AND
*A CENT SIGN WILL CANCEL THE TOTAL LINE AND RESULT IN 
*A NEW READ TO THE CONSOLE OR CARD READER. 

The *card reader*?  LOL.  I don't recall every having an interactive 
session with the card reader.  So it must have been a way to save on 
punched cards for SA-DDR: INPUT  3350 NO NO WRONG WRONG IGNORE 
THIS¢INPUT 111 3390 MYVOLRight.  Sure.  NOT.  You threw it away and 
typed a new one.  :-)

Alan Altmark
z/VM Development
IBM Endicott

Re: Automated DDR funny - has anyone got any ideas

[Mike Walter]

What happens if your control statement volser matches the volser reported 
by DDR, e.g.
OUT D5F3 DASD v...@d5f3

Is the actual DASD volser being written to really d...@d543, or actually 
v...@d5f3 as reported by DDR?

Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.



"Colin Allinson"  

Sent by: "The IBM z/VM Operating System" 
03/10/2010 05:44 AM
Please respond to
"The IBM z/VM Operating System" 



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Automated DDR funny - has anyone got any ideas







I have a series of automated slaves that read a control file and perform 
DDR copies. These slaves do not have their own RW minidisks so they queue 
the commands for DDR. 

In this case the target volume has a label of d...@d5f3 but DDR is winging at 
a label mismatch. I have traced my exec and can see that the line :- 

OUT D5F3 DASD d...@d5f3 

is being correctly queued but DDR responds with :- 

HCPDDR711D VOLID READ IS v...@d5f3 NOT D5F3 

My first thought was CP TERM setting so I ensured that CHARDEL was set off 
- but to no avail. (I checked it with a FOR userid CMD Q TERM while it was 
waiting on a response). 

Does anyone have any ideas what is happening here? 


Colin Allinson

Amadeus Data Processing GmbH



The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by e-mail. 

Re: Automated DDR funny - has anyone got any ideas

[Nick Laflamme]

On Mar 10, 2010, at 7:07 AM, Colin Allinson wrote:

> 
> I should read the DDR help more carefully next time !! 
> 
> " When you use the CP TERMINAL command to redefine the CHARDEL and LINEDEL 
> characters, the redefinitions have no effect  on DDR line editing. DDR 
> continues to recognize the at sign (@) and the cent  sign (¢) as valid 
> CHARDEL and LINEDEL symbols, respectively." 

I'd be very tempted to open a PMR and "request" they also respect an ESCAPE 
character. It's only fair.

But that's a long-term solution, not a short-term solution. :-( 


Nick

Re: Automated DDR funny - has anyone got any ideas

[Dieltiens Geert]

Colin,
 
>From HELP DDR: 
 
"Two logical line editing symbols are recognized and handled by the DDR   
command. The first is the logical character-delete symbol (@) that allows
deletion of one or more of the previous characters entered. The second is the
logical-line delete symbol ([) that deletes the entire previous physical line
Most often, the default values for these two symbols are defined for each
virtual machine at system generation. When you use the CP TERMINAL command to
redefine the CHARDEL and LINEDEL characters, the redefinitions have no effect
on DDR line editing. DDR continues to recognize the at sign (@) and the cent 
sign ([) as valid CHARDEL and LINEDEL symbols, respectively."
 
Bye,
Geert.

 
 

_ 
Geert Dieltiens 
Systeembeheerder 
Informatica J. Van Breda & C° 
Tel.: + 32 3 217 50 16 

 



From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf 
Of Colin Allinson
Sent: woensdag 10 maart 2010 12:45
To: IBMVM@LISTSERV.UARK.EDU
Subject: Automated DDR funny - has anyone got any ideas



I have a series of automated slaves that read a control file and perform DDR 
copies. These slaves do not have their own RW minidisks so they queue the 
commands for DDR. 

In this case the target volume has a label of d...@d5f3 but DDR is winging at a 
label mismatch. I have traced my exec and can see that the line :- 

OUT D5F3 DASD d...@d5f3 

is being correctly queued but DDR responds with :- 

HCPDDR711D VOLID READ IS v...@d5f3 NOT D5F3 

My first thought was CP TERM setting so I ensured that CHARDEL was set off - 
but to no avail. (I checked it with a FOR userid CMD Q TERM while it was 
waiting on a response). 

Does anyone have any ideas what is happening here? 


Colin Allinson

Amadeus Data Processing GmbH


DISCLAIMER

This email and any files transmitted with it are confidential 
and intended solely for the use of the individual or entity 
to whom they are addressed. If you have received this email 
in error please notify postmas...@vanbreda.be
This footnote also confirms that this email has been checked 
for the presence of viruses.

Informatica J.Van Breda & Co NV BTW BE 0427 908 174

Re: Automated DDR funny - has anyone got any ideas

[Colin Allinson]

I should read the DDR help more carefully next time !!

" When you use the CP TERMINAL command to redefine the CHARDEL and LINEDEL 
characters, the redefinitions have no effect  on DDR line editing. DDR 
continues to recognize the at sign (@) and the cent  sign (¢) as valid 
CHARDEL and LINEDEL symbols, respectively."

 

Colin Allinson

Amadeus Data Processing GmbH

Re: Automated DDR funny - has anyone got any ideas

[Colin Allinson]

"Imler, Steven J"  wrote:-

> To be sure try ... d...@d5f3

OK - tried that but it showed that it was trying to match to VD5F3. This 
suggests that @ is still operating as CHARDEL even though it is set OFF.

Just to clarify - all TERM characters (except LINEND) are OFF 

   >L> "PIPE CP Q TERM | CONS" 
LINEND  # , LINEDEL OFF, CHARDEL OFF, ESCAPE OFF, TABCHAR OFF 
LINESIZE 000, ATTN ON , APL OFF, TEXT OFF, MODE VM, HILIGHT OFF 
CONMODE 3215, BREAKIN   IMMED , BRKKEY PA1  , SCRNSAVE OFF 
AUTOCR ON , MORE 050 010, HOLD ON , TIMESTAMP OFF, SYS3270 OFF  

So, I tried something else and doubled up the @ sign (so I queued OUT D5F3 
DASD V@@D5F3). Now this is really strange - I got the message :-
 
HCPDDR711D VOLID READ IS v...@d5f3

So it seems that DDR knows the label sort of matches but not to what it 
was given. Looks like something funny within DDR. 

Colin Allinson

Amadeus Data Processing GmbH

Re: Automated DDR funny - has anyone got any ideas

[Imler, Steven J]

To be sure try ... D"@D5F3

 

JR (Steven) Imler
CA 
Senior Sustaining Engineer
Tel: +1-703-708-3479
steven.im...@ca.com
 

 

From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Colin Allinson
Sent: Wednesday, March 10, 2010 06:45 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Automated DDR funny - has anyone got any ideas

 


I have a series of automated slaves that read a control file and perform
DDR copies. These slaves do not have their own RW minidisks so they
queue the commands for DDR. 

In this case the target volume has a label of d...@d5f3 but DDR is winging
at a label mismatch. I have traced my exec and can see that the line :- 

OUT D5F3 DASD d...@d5f3 

is being correctly queued but DDR responds with :- 

HCPDDR711D VOLID READ IS v...@d5f3 NOT D5F3 

My first thought was CP TERM setting so I ensured that CHARDEL was set
off - but to no avail. (I checked it with a FOR userid CMD Q TERM while
it was waiting on a response). 

Does anyone have any ideas what is happening here? 


Colin Allinson

Amadeus Data Processing GmbH