I am working on a training instance, setting up calendar examples. I noticed the field length for a calendar description is 1,204 characters, yet the length of a job description is less (11.3.6 SP5 or so).
Would it make sense for these to match?
Likewise, should the allowable character fields be the same? (like quotes, other special characters)
I imagine you would need to provide a more detailed description for a calendar that covers multiple jobs and/or time periods versus a description for one single job. For a job description, you would want to keep it short and sweet. I think 1,204 characters in a job description would be a bit much, especially if you are looking at a job definition as JIL.
Example: The first job has a description with 256 characters and the second description has 1,204 chracters.
/* ----------------- sleep ----------------- */
insert_job: sleep job_type: CMDcommand: sleep 15machine: redhat-1136sp6owner: autosys@redhat-1136sp6permission:date_conditions: 1days_of_week: mo,tu,we,th,frstart_mins: 00,10,20,30,40,50description: "L6GXRuQw619tesKhea72W4J33pBN2Wk8lCqF0Ul1px20pPpcAM8GZOaqJDgBlhST7WrnxIKecseanr2HeXT0C336UCizT7syaP9X2ojkBHtTo0n8svpYvuuc6FicRijBgpLijREk4Yy4oK8HVgPJMs44f2YbwCJNIWIaEQAjLfOrubSsDzlOx9pZbtlWvifSbOXLStgEBvpvtcUGnaBCXRI0VvCSwPCcQvQJQo8vN1hJZFeCeu81B2jQ8tGu8Pum"alarm_if_fail: 1
We, and other customers, have jobs and calendars that are simple, and others more complex. We might have a calendar that can be easily described, as in "UK Bank Holidays" or one that is more complicated depending on the specific business logic. As it stands, we have been given a rather long field for calendars, and half that for jobs.
AutoSys "jobs" also include boxes, so I think it is unfair to claim job descriptions should be "short and sweet". We have boxes that include multiple sub-boxes, and dozens if not hundreds of jobs. The top-level box description field should allow sufficient size to capture notes about how that box was designed, when it is expected to run, and other business details.
There are likely to be multiple external repositories where the workflow is documented, including change control systems, operation, maintenance, and escalation instructions. Leaving room for lengthy URLs to those systems of record seems a reasonable request.
Jim, might this be a good thing to add as an idea?
Lenn - yes, I thought about that and posted it as a question first, to gauge what others think before going the Idea route. So far, no other customer comments. If anyone joins the bandwagon I will create the Idea.
I also "unmarked" the provided reply since it is not correct, in the OP opinion. (that's me).