Sponsored Content
Operating Systems AIX Horribly old stuff: SMS disks for IBM PC 850? Post 302188002 by dlundh on Tuesday 22nd of April 2008 12:34:29 PM
Old 04-22-2008
Horribly old stuff: SMS disks for IBM PC 850?

Hi.

I'm trying to reinstall AIX 4.3.3 (ML9) on an IBM PC 850 PowerPC machine but I have trouble getting an SMS diskette that will let me set the CD as bootable.

The SMS diskette I have is 1.26 and it either crashes or lists Hard Disk 0 some 20 + times (and nothing else) on the screen you choose the boot drive from.

Is there a newer (or older?), less buggy, version of SMS for PC 850? There is, to the best of my knowledge no problem with the hardware in the machine. I can use both CD-ROM and diskette from AIX on the machine right now.
 

6 More Discussions You Might Find Interesting

1. AIX

new IBM pseries and new disks

Hello Gurus, i'm quite new person in AIX world, actually i'm SAP consultant. But due to my job faced with AIX. Trying to configure new server for installation SAP. We have 4 disks one of them (hdisk3) has VG rootvg. How i can extend rootvg with another disk? i tried: # extendvg rootvg hdisk0... (2 Replies)
Discussion started by: sapbcer
2 Replies

2. High Performance Computing

IBM Scheduler for High Throughput Computing on IBM Blue Gene P

A lightweight scheduler that supports high-throughput computing (HTC) applications on Blue Gene/P. (NEW: 06/12/2008 in grid) More... (0 Replies)
Discussion started by: Linux Bot
0 Replies

3. Solaris

Sol10 on primepower 850

I've got a console that seems to be hung. all other services (ip, etc) work perfectly. in fact, its still in production... we just don't have console access. so i there are two consoles on this guy.. scfc0 and scfc1. using iompadm from fujitsu, this is what i got: # ./iompadm -c FJSVscf3 info... (1 Reply)
Discussion started by: pupp
1 Replies

4. Red Hat

IBM RAID disks

We have a Red Hat linux server running on IBM x445 hardware. There are external disks in an IBM EXP300 disk enclosure. The system is running RAID 5. One of the four IBM disks (73.4 GB 10k FRU 06P5760) has become faulty. The system is still up and running OK because of the RAID. In that same EXP300... (3 Replies)
Discussion started by: pdudley
3 Replies

5. AIX

Wanted: Thinkpad 800 systems (820, 850, 860, etc) (ppc 603e)

Hello everyone, I'm working on a for-fun project where I'm assembling a mass of various old computers, including a number of earlier UNIX workstations. They will be on display at a number of east coast conferences (HOPE, Shmoocon, etc). I'm trying to find a Thinkpad 860, 850, 820 or one... (1 Reply)
Discussion started by: telmnstr
1 Replies

6. AIX

IBM Virtual Machine OS on intel x86 and x64? IBM AIX OS on IBM Virtual Machine?

Hi There, I have zero information and zero knowledge for IBM virtual machine except Amazon cloud and VMware ESXi (Only Linux OS available). Anyone could provide me the following answer - Can IBM VM been deploy on X86 and X64 (Intel Chip)? If answer is yes any chance to deploy AIX OS... (13 Replies)
Discussion started by: chenyung
13 Replies
GSMSMSD(8)						      System Manager's Manual							GSMSMSD(8)

NAME
gsmsmsd - SMS message reception daemon SYNOPSIS
gsmsmsd [ -a action ] [ --action action ] [ -b baudrate ] [ --baudrate baudrate ] [ -c concatenatedID ] [ --concatenate concatenatedID ] [ -C service centre address ] [ --sca service centre address ] [ -d device ] [ --device device ] [ -D ] [ --direct ] [ -f ] [ --flush ] [ -h ] [ --help ] [ -I init string ] [ --init init string ] [ -r ] [ --requeststat ] [ -s spool directory ] [ --spool spool directory ] [ -t SMS store name ] [ --store SMS store name ] [ -v ] [ --version ] [ -X ] [ --xonxoff ] { sms_type } DESCRIPTION
gsmsmsd reads new incoming SMS from the mobile phone and dispatches them to a user-defined action. Additionally it can send SMS message that it reads from a spooldir. gsmsmsd attaches itself to the device given on the command line (usually an GSM modem) using the specified baudrate and waits for incoming SMS messages. If no device is given, the device /dev/mobilephone is used. If no baudrate is given, a default baud rate of 38400 is used. If no action is given, the SMS message is printed to the standard output. If an action is specified the action is excecuted using the shell and the SMS message is written to the standard input of the action. gsmsmsd needs one empty storage slot for SMS messages in the mobile phone, otherwise SMS reception will not work. The SMS store to use for temporary storage of incoming SMS can be selected using the --store option, otherwise the ME default store is used. To terminate gsmsmsd cleanly (without losing SMS messages) one should send either SIGINT (CTRL-C on the command line) or SIGTERM to the process. Error messages are printed to the standard error output. If the program terminates on error the error code 1 is returned. sms_type may be any combination of: sms, no_sms Controls reception of normal SMS messages. cb, no_cb Controls reception of cell broadcast messages. stat, no_stat Controls reception of status reports. The default is sms, cb, and stat. OPTIONS
-a action, --action action The action to execute for each incoming SMS message. If no action is given the SMS is written to the standard output. -b baudrate, --baudrate baudrate The baud rate to use. -c concatenatedID, --concatenate concatenatedID If an ID is given, large SMSs are split into several, concatenated SMSs. All SMSs have the same ID and are numbered consecutively so that the receiving phone can assemble them in the correct order. IDs must be in the range 0..255. This number is increased by one for every outgoing concatenated SMS and wraps around after 255. Not all receiving phones will support concatenated SMSs (and dis- play them as separate SMSs), since all the numbering and ID information is carried in the user data header element at the beginning of the SMS user data. This information may show up as garbage in such phones. -C service centre address, --sca service centre address Sets the service centre address to use for all SUBMIT SMSs (may not work with some phones). -d device, --device device The device to which the GSM modem is connected. The default is /dev/mobilephone. -D, --direct Enables direct routing of incoming SMS messages to the TE. This is not supported by many mobile phone/GSM modem combinations. There- fore, the default is to store incoming SMS temporarily before processing them in the indicated store. -f, --flush This option causes gsmsmsd to flush (ie. read and erase) existing SMS messages from the SMS store selected by the --store option. The action given by the --action option is executed on each of the flushed SMS. This option should be used to ensure that enough space is available in the SMS store for temporary storage of incoming SMS, otherwise incoming SMS might be ignored silently by the ME. -h, --help Prints an option summary. -I init string, --init init string Initialization string to send to the TA (default: "E0"). Note that the sequence "ATZ" is sent first. -r, --requeststat Request status reports for sent SMS. Note: This option only makes sense if the phone supports routing of status reports to the TE. Otherwise the status reports might show on the phone's display or get lost. -s spool directory, --spool spool directory This option sets the spool directory where gsmsmsd expects SMS messages to send. The format of SMS files is very simple: The first line contains the phone number of the recipient. Everything else after the first line is interpreted as the SMS text. Please refer to gsmsendsms(1) for details on the SMS text character set and maximum length. gsmsmsd polls the spool directory every 5 seconds. Sent SMS message files are removed. -t SMS store name, --store SMS store name The name of the SMS store to read from (for the --flush option) or write to (for temporary SMS storage). This option must be must be used in conjunction with the --flush option. If this option is omitted the ME uses it's default SMS store for temporary storage of incoming SMS. A commonly available message store is "SM" (SIM card). -v, --version Prints the program version. -X, --xonxoff Uses software handshaking (XON/XOFF) for accessing the device. EXAMPLES
The following invocation of gsmsmsd sends each incoming SMS message as a mail to the user "smsadmin": gsmsmsd -d /dev/ttyS2 -b 19200 -a "mail smsadmin" This is the format of SMS deliver messages as output from gsmsmsd: ---------------------------------------------------------------- Message type: SMS-DELIVER SC address: '491710762100' More messages to send: 1 Reply path: 0 User data header indicator: 0 Status report indication: 0 Originating address: '01805000102' Protocol identifier: 0x39 Data coding scheme: default alphabet SC timestamp: 17.12.98 14:10:55(+0100) User data length: 159 User data header: 0x User data: 'Nicht vergessen! Die XtraWeihnachtsverlosung lauft noch bis zum 24.12. Nutzen Sie jetzt Ihre Gewinnchance und faxen Sie Ihren Teiln.-Gutschein an 0180/5000 056' ---------------------------------------------------------------- This is the format of SMS status report messages as output from gsmsmsd: ---------------------------------------------------------------- Message type: SMS-STATUS-REPORT SC address: '' More messages to send: 0 Status report qualifier: 0 Message reference: 0 Recipient address: '' SC timestamp: 00.00.00 00:00:00(+0000) Discharge time: 00.00.00 00:00:00(+0000) Status: 0x0 'Short message received by the SME' ---------------------------------------------------------------- The following invocation of gsmsmsd flushes all existing messages from the "SM" SMS store and looks in the "/tmp/spooldir" directory for SMS to send: gsmsmsd -d /dev/ttyS2 --spool /tmp/spooldir -f --store sm --action 'mail smsadmin' FILES
/dev/mobilephone Default mobile phone device. AUTHOR
Peter Hofmann <software@pxh.de> BUGS
Cell broadcast SMS message reception has not been tested, but it has been enabled in the gsmsmsd daemon. The mobile phone device is blocked when the gsmsmsd daemon is running, ie. it cannot be used for data transfer or from the other programs of this suite (gsmpb, gsmsms). Report bugs to software@pxh.de. Include a complete, self-contained example that will allow the bug to be reproduced, and say which version of gsmsmsd you are using. COPYRIGHT
Copyright (C) 1999 Peter Hofmann gsmsmsd is free software; you can redistribute it and/or modify it under the terms of the GNU Library General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. gsmsmsd is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Library General Public License for more details. You should have received a copy of the GNU Library General Public License along with gsmsmsd; see the file COPYING. If not, write to the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. SEE ALSO
gsminfo(7), gsmpb(1), gsmctl(1), gsmsendsms(1), gsmsmsstore(1). gsmsmsd v1.10 Sat Jun 16 22:10:00 UTC 2012 GSMSMSD(8)
All times are GMT -4. The time now is 10:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy