@C_R  I think my original post was a bit snarky; I apologize for that. I really was being sarcastic when I suggested that the dicumentation for the description option was sabotage, 

However, it would be very simple to write a few lines of code that would allow a user to write describe (f) or description(f) or Description (f) . There is a difference between being being picky and being precise. Successful products, web sites, etc. are user friendly. They bend over backwards to understand what the customer wants. 

An example is the Help facility. If you look up procedure you get many pages of detail nefore you get to an example. That is completely backwards from what would be helpful. Most people want a simple example followed by more complicated examples foloowed perhaps by something more encyclopedic-not the othe way round.

To verify my assertions ask yourself when you ever read the instructions for a new product/device/program before using it. Most of us cheat-the quickstart blurb is as far as we get.

I think Maple Help pages are written by very competent and knowledeable users/developers. That is not what I want. If I want to use some feature on my phone I ask a grandchild how to do it and get a straightforward answer.

@nm Many thanks. I looked at it for many hours without spotting my error.

I wonder if there is an AI "supervisor" that might be able to help with such errors. As I age I find I am more prone to waste time hunting for my mistakes.

@acer Thanks-I will check the document

@acer Thanks for clarification.

@dharr I think I get it. How does Maple know the size of the Array xpts?

Also, I am happy with eval(...,a=20) etc rather than parameters I though that was disparaged now.

@acer Thank you. I will copy your answer and apply it to my problem. 

What I would really like is the syntax to get a vector with entries y1(xn) corresponding to one parameter value and another vector with entries y2(xn) corresponding to another parameter value. The point being that I want the same xn values for each vector. I could of course just make up my list of xn's -say equally spaced over the range-and then call ds0lve 500 times for each parameter value but I am sure that if I call ans(1.7) where ans :=dsolev(eq...) it will compute many intermediate values abyhow so I thought I could speed things up by asking for those values. Since I suspect that dsolve uses adaptive step sizes the call for ans(1.7) with another parameter values might well have different xnn values.

@nm Many thanks.

@nm If I do

"If you do not want to explicitly add the read() to each worksheet which needs the shared code, you can put this read() command in your maple .ini file so it is read automatically each time you start/open a worksheet."

won't all that junk get added to all worksheets I open whether related to the project or not?

@acer 

Thank for the explanation. I never thought of opening the file ina text editor.

@acer 

Thanks for your suggestion.

I am a sloppy typist and I wonder if perhaps I enterred control something rather than option something when I was trying for a Greek lettter or some such. If the 'character"  was invisible that would explain why I could not figure out what was happening. How did you find out the XML property view="presentation" part?

@Scot Gould dead_command.mw

Thanks for showing me how to upload worksheets.

The file is part of a project but it exhibits the problem I have. I cannot copy the command into a Maple prompt region.

Thanks for your interest.

@Scot Gould 

As I said, I can type in the commands (even with mis-spellings) and iy is okay. Why cannot I copy the text? What type of region does it copy to? There is no Maple prompt.

@Scot Gould 

I can't find any instructions.When I try to drag and drop it says "file format not supported"

I forgot to insert the command.
>

thans:= proc(z, T)
nansev(parameters = [z]);
namsev(T)
end proc;

Thank you.

It seems to me that there are quite a few very knowledgeable people at Maple. I have received much help from them over the years and I am grateful to them. BUT, perhaps some less savvy people are needed to test new packages, commands, etc. to see if the everage user can quickly get up to speed without having to ask for special help. In particular, help pages should have enouh clear examples so that one can quickly grab ab example and use it as a template withou having to read an explanation. (With all due respect, I always advise my students to skip the wordy and sometimes mysterious descriptions and go straight to the examples.)