Re: User space editor in iSphere - get "No editor selected" error

Vern,

There currently is nothing in iSphere which allows you to edit a user space as the "entire content". (Thought strictly speaking you can create an editor with one [long] character field and see the data that way, though it probably won't show you much that is useful in the non character fields.)

Editing a user space, such as comes back from an API, is something else entirely, I think. To do that correctly the layout of the "fields" in the user space needs to be known. That is where the designer comes in. (And for those folk who have large *CHAR data areas with multiple "fields" an editor can be created to make visible sense of those too, or you can continue to treat the data area as one field equivalent to CHGDTAARA.)

Sam

(comments all based on what iSphere 2.6.0 does.)


On 6/12/2015 2:47 PM, Vernon Hamberg wrote:

Thx paul - you got it - part of my confusion is, if I right-click a user
space, it gives me 2 options - iSphere User Space Monitor and iSphere
User Space Editor. I would never have thought to look at Data Spaces in
the help.

The help does say this - "From a programmer's point of view, both
objects are very similar; essentially each is a string of bytes"

Then there's this designer to make an "editor" that breaks out the
various values, "fields", etc.

All that seems good - I've not made it work for what I want yet.

I am confused that there IS a separate data area section in the help -
but I've used this and like it - it is like CHGDTAARA but the original
value is displayed, which the command does not do. No "editor" is needed
for this, to break up the value into its "format". I DO have examples
where having that format would be useful.

I haven't got this far - but it seems one must "assign" an editor to
each specific object. I hope that's not true, but it looks that way.
Maybe that's OK for some stuff, not sure if it aligns with change
management tools, though - just asking.

I really want something like EDTF and DSPF for use spaces - see, I do
NOT see data areas and user spaces as being the same "...from a
programmer's point of view..." - at least, not all the time.

So if I have not specified a layout - and this is NOT practical with
many of the APIs, due to varying lengths and all manner of offsets and
lists that vary in number - I want to have the ability to simply work
with the entire contents - and handle bytes that are not displayable -
the stuff before x'40', for example.

I look forward to future develoopments in this arena - hope my thoughts
are helpful!

Vern