Re: Saving SOCKETs

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

Hi Joe,

Sounds like they're unix domain sockets.  They aren't actually data files, 
they're just objects for interprocess communications.  I don't know that 
I've ever seen the error you've described, but I don't see any advantage 
to backing these up -- they don't contain any data, so you won't lose 
anything if you don't back them up.

If they're not restored, it shouldn't hurt anything, as soon as the 
programs that use them are started, they'll automatically be created.

What are they?  They're unix domain sockets.  If you're familiar with TCP 
sockets, they're the same sort of thing, except that they use a path name 
instead of a network address & port.  For communication between two 
programs on the same system, they're safer than TCP sockets because 
they're not accessible from other systems.

Usually, on our platform, we use data queues for stuff like this, but when 
software is ported from Unix or you get Unix weenies writing software, 
they might use Unix-domain sockets instead. :)


> During backup, we're getting errors on SOCKET objects in
> /QIBM/ProdData/OS400/Servers.  These look to be related to the standard
> sockets for the host servers, but just recently we started noticing errors
> in the backup procedure.  The error is CPD3775, Cannot save or restore
> /QIBM/ProdData/OS400/Servers/xxxxx.end, where xxxxx is something like
> central or signon.  We may have been getting these for some time and just
> now noticed them, but I was wondering if anybody else had this issue, and
> just for my edification, what the ramifications are in a save/restore
> environment: can you actually save and restore these objects?  What exactly
> are they?  (The second level text says you can ignore these messages in a
> system save, so my guess is that they aren't meant to be restored.)