Sponsored Content
Full Discussion: Problem with bosboot
Operating Systems AIX Problem with bosboot Post 302924718 by bobochacha29 on Wednesday 12th of November 2014 04:47:43 AM
Old 11-12-2014
Thanks guys. Maybe there was something wrong with the altinst_rootvg. I removed it and recreated it. Then I booted the hdisk7 from SMS ( no bosboot or bootlist commands anymore ) and it worked.
This User Gave Thanks to bobochacha29 For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

bosboot problem please help!

each time I try to do a bosboot or a mksysb the cpu says that he doesn't find /unix... I don't understand cause the kernel is here on the computer and at this exact place with the right name. I tried to force with -k /unix but it doesn't do anything. He doesn't find it and it is here... Do you... (6 Replies)
Discussion started by: jericho
6 Replies

2. AIX

bosboot: Boot image is 22995 512 byte blocks.

My mksysb scripts gives the following text on standard error: bosboot: Boot image is 22995 512 byte blocks. How come on a Aix 5200-07 aix-system. I thought this message meant that the tape (/dev/rmt0) is not bootable, but I read about a limit of 12 MB and 22995 block is less than 12 MB ... (0 Replies)
Discussion started by: frankwiel
0 Replies

3. AIX

installp -C error: 'bosboot verification failed'

Hi, I'm a noob with AIX, can anybody help me solve this issue I'm stuck with on an 5.3 box. bash# installp -C 0503-409 installp: bosboot verification starting... 0503-497 installp: An error occurred during bosboot verification processing. Thanks. (4 Replies)
Discussion started by: thebytegrill
4 Replies

4. AIX

has bosboot command changed characteristics of boot image?

hi all i just found one of my p650 server showing a warning message when i tried to run bosboot command after upgrading TL to AIX 530803. i also tried to run chpv -c hdisk0 and chpv -c hdisk1 to clear out the old boot info in hdisk0 and hdisk1 and rerun bosboot -a. it still showed... (0 Replies)
Discussion started by: rs6000er
0 Replies

5. AIX

bosboot issue

bosboot -ad hdisk0 give the following error .. malloc failed 0301-177 A previous bosdebug command has changed characteristics of this boot image. Use bosdebug -L to display what these changes are. 0301-106 /usr/lib/boot/bin/mkboot_chrp: The malloc call failed for size: 216174592 ... (1 Reply)
Discussion started by: b_manu78
1 Replies

6. AIX

user login problem & Files listing problem.

1) when user login to the server the session got colosed. How will resolve? 2) While firing the command ls -l we are not able to see the any files in the director. but over all view the file system using the command df -g it is showing 91% used. what will be the problem? Thanks in advance. (1 Reply)
Discussion started by: pernasivam
1 Replies

7. AIX

Cannot uninstall powerpath - bosboot issues

Hi Guys, I have a problem while trying to upgrade to more current EMC powerpath software on AIX 5.3 - respectively uninstalling the existing one. I tried to deinstall the powerpath software with removed disks - was working perfectly fine on 12 servers - but number 13 is failing with errors: ... (4 Replies)
Discussion started by: zxmaus
4 Replies

8. IP Networking

Problem with forwarding emails (SPF problem)

Hi, This is rather a question from a "user" than from a sys admin, but I think this forum is apropriate for the question. I have an adress with automatic email forwarding and for some senders (two hietherto), emails are bouncing. This has really created a lot of problems those two time so I... (0 Replies)
Discussion started by: carwe
0 Replies

9. AIX

bosboot issue

Hi i wanted to know for what reasons, bosboot fails with the error below.? # /usr/sbin/bosboot.dp -a -p /usr/lib/boot/chrp.disk.proto -d /dev/ipldevice dd: 0511-053 The write failed. : There is a request to a device or address that does not exist. 65893+1 records in. 1029+1 records out. ... (1 Reply)
Discussion started by: gnakul
1 Replies

10. UNIX for Dummies Questions & Answers

sed Or Grep Problem OR Terminal Problem?

I don't know if you guys get this problem sometimes at Terminal but I had been having this problem since yesterday :( Maybe I overdid the Terminal. Even the codes that used to work doesn't work anymore. Here is what 's happening: * I wanted to remove lines containing digits so I used this... (25 Replies)
Discussion started by: Nexeu
25 Replies
SMS::Send(3pm)						User Contributed Perl Documentation					    SMS::Send(3pm)

NAME
SMS::Send - Driver-based API for sending SMS messages SYNOPSIS
# Create a sender my $sender = SMS::Send->new('SomeDriver', _login => 'myname', _password => 'mypassword', ); # Send a message my $sent = $sender->send_sms( text => 'This is a test message', to => '+61(4) 1234 5678', ); # Did the send succeed. if ( $sent ) { print "Message sent ok "; } else { print "Failed to send message "; } DESCRIPTION
"SMS::Send" is intended to provide a driver-based single API for sending SMS and MMS messages. The intent is to provide a single API against which to write the code to send an SMS message. At the same time, the intent is to remove the limits of some of the previous attempts at this sort of API, like "must be free internet- based SMS services". "SMS::Send" drivers are installed separately, and might use the web, email or physical SMS hardware. It could be a free or paid. The details shouldn't matter. You should not have to care how it is actually sent, only that it has been sent (although some drivers may not be able to provide certainty). METHODS
installed_drivers The "installed_drivers" the list of SMS::Send drivers that are installed on the current system. new # The most basic sender $sender = SMS::Send->new('Test'); # Indicate regional driver with :: $sender = SMS::Send->new('AU::Test'); # Pass arbitrary params to the driver $sender = SMS::Send->new('MyDriver', _login => 'adam', _password => 'adam', ); The "new" constructor creates a new SMS sender. It takes as its first parameter a driver name. These names map the class names. For example driver "Test" matches the testing driver SMS::Send::Test. Any additional params should be key/value pairs, split into two types. Params without a leading underscore are "public" options and relate to standardised features within the SMS::Send API itself. At this time, there are no usable public options. Params with a leading underscore are "private" driver-specific options and will be passed through to the driver unchanged. Returns a new SMS::Send object, or dies on error. send_sms # Send a message to a particular address my $result = $sender->send_sms( text => 'This is a test message', to => '+61 4 1234 5678', ); The "send_sms" method sends a standard text SMS message to a destination phone number. It takes a set of named parameters to describe the message and its destination, again split into two types. Params without a leading underscore are "public" options and relate to standardised features within the SMS::Send API itself. text The "text" param is compulsory and should be a plain text string of non-zero length. The maximum length is currently determined by the driver, and exceeding this length will result in an exception being thrown if you breach it. Better functionality for determining the maximum-supported length is expected in the future. You input would be welcome. to The "to" param is compulsory, and should be an international phone number as indicated by a leading plus "+" character. Punctuation in any form is allowed, and will be stripped out before it is provided to the driver. If and only if your driver is a regional driver (as indicated by a ::-seperated name such as AU::Test) the "to" number can also be in a regional-specific dialing format, "without" a leading plus "+" character. Providing a regional number to a non-regional driver will throw an exception. Any parameters with a leading underscore are considered private driver-specific options and will be passed through without alteration. Any other parameters without a leading underscore will be silently stripped out and not passed through to the driver. After calling "send_sms" the driver will do whatever is required to send the message, including (potentially, but not always) waiting for a confirmation from the network that the SMS has been sent. Given that drivers may do the actual mechanics of sending a message by quite a large variety of different methods the "send_sms" method may potentially block for some time. Timeout functionality is expected to be added later. The "send_sms" returns true if the message was sent, or the driver is fire-and-forget and unable to determine success, or false if the message was not sent. SUPPORT
Bugs should be reported via the CPAN bug tracker at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=SMS-Send <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=SMS-Send> For other issues, contact the author. AUTHOR
Adam Kennedy <adamk@cpan.org> COPYRIGHT
Copyright 2005 - 2011 Adam Kennedy. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of the license can be found in the LICENSE file included with this module. perl v5.14.2 2012-04-07 SMS::Send(3pm)
All times are GMT -4. The time now is 06:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy