Linux on 390 Port <LINUX-390@VM.MARIST.EDU> wrote on 07.10.2005 17:35:05:
> > vmcp has a return value, which you can check in scripts. > > e.g: > > > > # vmcp <some large query> > > # echo $? > > > > 0 stands for everything is fine, any other value for problems. > > vmcp returns ENOBUFS (105) if the buffer was not large enough > > That means the output was larger than 64kb. > > Usability suggestion: since this is a VM-specific widget, could you return > codes that are consistent with the implementation of DIAG 8 on CMS? I think > it would help in understanding how to use the gadget, and folks coming over > from CMS would be more familiar with those return codes. David, I beg you pardon, but i don't like the CP return code approach. While a VM "widget" it is nonetheless a Linux module and should adhere to Linux return code principles. But your point is well taken, it would certainly be valuable to describe how those get mapped to Linux values. > > > > If there is a consensus that vmcp should always print > > something to stderr if the buffer was not large enough, tell > > us and we can add that. > > A combination of the "familiar" return codes noted above, and an explanatory > message to stderr would be my preferred approach. > > -- db > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 Ingo ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
